Once an issue is assigned to a user, will still he be able to edit in this issue?
I don't want a user not assigned for an issue to be able to edit issue's status. For example , a dev worked on a bug, then I assigned to QA to test, I don't want dev person to be able to click on buttons related to QA .Now dev is able to.
It depends on how you set it up, and there are two layers here.
First, look at the project permission scheme. This says things like "Issue Edit: Reporter, Assignee and members of the role called developer". It sounds to me like you need to go over the permissions and check they do what they need. Specifically the "edit" permission here - you probably want that to say just "assignee"
Secondly, status - this is NOT a field, it is just a display telling you where an issue is. You can NOT edit status, as there's nothing there to edit. You change status by moving issues through a workflow. The workflow transitions (the action of moving from status to status) have things called "conditions", which are rules on who can perform the transitions. So, for example, a transtion from "ready to test" to "being tested" might have the condition "only people in the QA group can do this"
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Planning and grooming sessions all come with their own sets of rules. Team members meet to estimate stories or other work items, all according to an agreed-upon process. And with every session comes ...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs