Software Development Workflow Scheme > workflow

Why does it auto-reassign an issue to the project owner when an issue is moved on a kanban board? And how do I change this to retain the assigned user when an issue is moved?

2 answers

This widget could not be displayed.

You might check your workflow and see if the transitions have post functions which are assigning the issue.

 

A screenshot of the workflow is attached. I don't know what I'm looking for or what to change. Can you advise?

Screen Shot 2016-04-27 at 11.31.02 AM.png

Difficult to say what could be going on here but it may be related to this article

https://confluence.atlassian.com/jirakb/configuring-auto-assign-779158849.html

If you switch to graphical view on the workflow I think it is easier to follow. When you move an issue to In Progress I suspect you are clicking a button called Start Progress. This button executes a transition. Click on the transition labelled Start Progress in the workflow diagram. A dialog box should appear showing the details for the transition. Click on post-functions.

The list of post functions for that transition should be displayed. Check the names on them and see if any are set up to change the assignee.

 

Chris

I read the article. And I looked at the workflow rules. The rule is in place to allow assignment:

Assign the issue to the current user. Please note that the issue will only be assigned to the current user if the current user has the 'Assignable User' permission.

And the user is part of a developer group that I believe has Assignable User perms (I did not remove it). Although I'm not real clear on how to verify that. Do you know?

Attached is a graphical view screenshot. Users do not click a Start Progress button, they simply drag the issue from To Do column to the In Progress column and it gets re-assigned to me (project owner). Ss of post functions also attached. 

Screen Shot 2016-04-27 at 12.59.39 PM.png

Screen Shot 2016-04-28 at 12.00.55 PM.png

Hey Chris Dunne, do you have any further thoughts here?

Did you try my suggestion to delete the 3rd postfunction?

Ok trying that. I don't have a lead dev defined, but maybe it's defaulting to the project owner. Will let you know. Thanks. 

It worked. Thanks Chris Dunne. 

Glad to help. Can you mark this as the answer?

This widget could not be displayed.

Hi Chris

The issue is caused by the 3rd post function. It says Assign the issue to the lead developer. If you were using components and had component leads assigned this would assign the issue to the component lead. If you are not using component leads, then it actually assigns the issue to the project lead...or at least that is what I expect is happening.

To resolve this just delete the 3rd post function. Hover over the right hand side of that row and you should see some icons - click the X icon to delete it. Your workflow will be in draft mode so don't forget to click the Publish Draft button. 

 

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Tuesday in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

145 views 1 3
Join discussion

Atlassian User Groups

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!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you