Hi
I have the problem that when moving from one status to another the users have to do two things:
1. Transition from one status to the next
2. Update the Assignee
Is there a way upon transtion to remind or insist that the user re-assigns ?
I also wondered if there was a way at a transition to only allow assigning to a certain group of users ?
Thanks so much
Jim
The act of completing the transition is expected to have JIRA automatically then change the status of the issue. However there is not really a means to force users to change that field during a transition natively within JIRA. JIRA can be configured to require a field value some value, but there is not a means to require a change be made to a field. At least not with the base code in JIRA at this time.
You might be able to do this with the use of a 3rd party plugin like JIRA Misc Workflow Extensions. I believe this plugin has the ability to add in new validators in workflows that can then require a field like assignee to be changed during transition.
In addition to that plugin, what you could do is to create a transition screen to appear when that transition is clicked. This would bring up a screen with fields you could choose to display there that could be filled out before the transition happens. Steps on how to do this are in https://confluence.atlassian.com/jirakb/mapping-a-screen-to-a-workflow-transition-720634253.html
This way when users execute this transition they could be prompted to see the field assignee.
Thanks a lot Andrew. That works really well. I added a transition screen with only Assignee. Pity is that the COMMENT field also appears. I guess there is no way to avoid this being displayed ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There was a bug listed on JRASERVER-12244 to request to have the ability to make that comment field optional. While it appears JIRA doesn't have a means to do this, there are some interesting comments from other customers that appear to have found ways to get around this. I'd recommend taking a look at Marius' response at https://jira.atlassian.com/browse/JRASERVER-12244?focusedCommentId=843433&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-843433
The suggestion there is to actually create another custom field that could be added on that screen, and then update the field description of that custom field in order to insert the javascript listed there. In turn that should be able to force that comment field not to display on that screen when the browser renders it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Andrew,
Thanks for the answer. I wanted to ask what happens when a user transitions an issue in the Scrum or Kanban board ? Will the transition screen appear ?
Thanks
Jim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This transition screen still appears when you transition this way on a scrum or kanban board.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.