Can I change another user's status on the task board without changing the assigned user to me? (PLEASE HELP)

[alex berg]

We want to use the taskboard for our scrum huddles (projecting on a wall). However, when I update status (done, in process, etc) for team members as they give their updates the tasks get reassigned to me (an admin) and fall off their view of the task board. This is making it impossible to use as I don't want to take the time to ask each person to log in before their udpates (too time consuming).

There has to be a way to address this right?

[Adam Saint-Prix · Accepted solution]

Great video.

At :48 into the video you show the GreenHopper General Configuration screen, where you have disabled the "Auto-Assign" check box option.

I believe this is the Global setting, but JIRA/GH also has project specific settings that can be configured. Try this:

1. Go to the task board screen you show for Josh_Project and Sprint 8.
2. Click on Tools>Configuration>General
3. Scroll Down to "General Configuration", just below Flagging Field.
4. Is "Auto-Assign" checked?

I tested it and it is possible for a single Project to have "Auto-Assign" enabled, even though the Global Configuration setting is disabled.

I think that might be your problem. See if the project specific configuration is overriding the Global Setting.

Also, you may want to check the proejct templates (Default and Scrum) to make sure the behavior matches what you'd like to see (no auto-assignment).

Hopefully that does the trick.

[alex berg]

Holy shi* you're my fuc*ing hero. You deserve a badge, karma points, and a gold star on your parents' refrigerator for rescuing the princess.

[JamieA]

Disable auto-assign in the greenhopper config. Then modify your workflow so that the start and stop progress doesn't have the "assigned to current user" condition.

[alex berg]

I found the auto-assign (thanks so much). Now I'm digging to see where in the workflow I can make the other change you mention. I'm using the default work flow right now and am not seeing the assigned to current user condition applied (not seeing it at all actually).

[JamieA]

Go to workflows, copy the jira workflow, go to Start Progress, look at Conditions.

I don't think you can create a draft of the default workflow, so you then need to modify the default workflow scheme, adding the edited workflow. Worthwhile testing in a play instance.

[alex berg]

Found it. I copied it, found the condition, and deleted it. Now I need to make the edited workflow my deginated workflow for this project. Searching for that...

[alex berg]

Wow, this is really frustrating. I find lots of copy referencing this in the tool, but none of it is linked making it actionable.

[JamieA]

You must not have disabled auto-assign in greenhopper - you've definitely disabled this: http://confluence.atlassian.com/display/GH/Managing+your+User+Preferences ?

[alex berg]

Tried the steps above and tasks, when moving from open to in progress are still re-assigning to me.

[alex berg]

I did. That was the easy part. Creating a new work flow, and then a new scheme, and then associating that scheme was the pain. I'm not sure I have it right, but it appears to be assigned. I've been spending a hour and half on this this morning reading through the docs. I've been using JIRA since 2004 and never had so much trouble. I wish there was a number I could call....any more suggestions? My colleagues are telling me to try a different product.

[alex berg]

here is a screen shot

[alex berg]

Here's a screen shot.

[Josh Marion]

I am having the exact same issue. When I am in the task board via Agile and I move a task over from Open to In Progress it assigns it to me, when in fact, I want it just to stay assigned to the developer. How can I disable this. I did all of the things in this post to no avail.

Thanks

[alex berg]

My attempts at this are still failing too. Here is a screenshot of my GH setting.

<img src="https://www.dropbox.com/s/8w2gx2qf88ez2zj/gh.jpg">

[alex berg]

FWIW - still having the same issue myself. My greenshopper box is unchecked as well.

[Josh Marion]

Still havin a similar issue running 5.0.3-rc1 Build # 729

Any thoughts out there about this issue? Alex, I feel your pain. I have also been using Jira since 2007

[Adam Saint-Prix]

What version of JIRA and GreenHopper are you guys using? And is your project using the default JIRA workflow and Scrum template for GH? Just want to see if I can duplicate the behavior.

[alex berg]

I am using the hosted version so I'm assuming it's just naturally the most current. I am no longer using the default workflow as I needed to modify it to remove the condition that re-assigns on task bar status change as the first commentor suggested. So, I copied the default workflow, gave it a new name, and removed the condition. I then created a new scheme as well and applied it. So far nothing has changed. I've also tried multiple times to post screenshots of my settings, but it keeps failing for me both when I browse to them and reference web images via the WYSIWYG tool.

I've been a JIRA user since 2005 or so and have never had so much trouble. Thanks so much for any help you can provide as I am beyond frustrated and need to get this fixed.

[Matt Doar]

I'm not sure if that Auto-Assign checkbox was a bug or a feature! Who was it auto-assigning to anyway in Classic GH?

[Adam Saint-Prix]

Good stuff. Feel free to mark as answered. Hopefully the story huddles go a little smoother now.

Best,

- Adam

[Adam Saint-Prix]

I'm guessing that worked! Sweet. :)

[alex berg]

Oh, yes. It worked. ; )

[Adam Saint-Prix]

Fair enough. I'm willing to screenshare if that helps too. Let me know.

[alex berg]

Here's a video of some of my settings.

http://youtu.be/5h-LVY-N_Lk

[Adam Saint-Prix]

Could it be that you have a default assignee configured based on a ticket's component? Is it possible that in the story huddle you are updating the task's component and based on this is it possible that the assignee is being set?

Hmmm...change of status. That's really weird. I feel like I would need to see it at this point, otherwise I'm just suggesting possible causes. Hard to say without seeing it.

[alex berg]

Tomorrow moring I will record a screen cast of my settings, show a demo of what is transipring, and then post it to you my You Tube account. ; )

[Adam Saint-Prix]

Alex,

Are you allowing unassigned issues in your project or does your project default tickets to be assigned to a project lead or someone else?

[alex berg]

We do not allow unassigned issues. I am the JIRA admin though (for what it's worth). When I, or another user with admin rights, changes the status the tasks automatically change the assignee. I've tried all the steps here - to no avail. Thanks for your continued help. Right now, after each scrum huddle, I have to go into JIRA and re-assign any tasks whose status was updated.