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?
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:
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.
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.
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.
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.
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.
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.
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.
We're looking for participants for a workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sha...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG