I'm afraid the question is a little unclear. What groups do you mean? (I'd guess at groups of users?) More importantly, what do you mean by "associate with status"? I really don't have any guess for what you might mean by that?
My workflow have 3 status: Status A, Status B and Status C.
so, in Status A I will wich only appears the field 'Assignee', 'Due Date'... in Status B i will wich the field 'Assignee', 'Due Date' and 'Contact' and finally, in Status B the fields 'Adress' and 'name'.
differents fields in diferent status...
Ok. You cannot really do this. A field belongs to an issue. That's it, it's nothing to do with the workflow.
You can, however, control where fields appear. If you look at "screen schemes", you will find that there are three entries - you can tell Jira to use a different "screen" (which is a list of fields to use) for View, Edit and Create issue. Those are shared actions, they take no account of status.
Secondly, in your workflows, which move issues between status, you can use "transition screens". They're the same theory as the view/edit/create - a list of fields to show to the users. So, with these, you can say "when going from status A to status B, show the user on;y the assignee and due date", "when going from B to C, show assignee, due date and contact". And so on.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
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