Hi Team,
When issue type Requirements Gathering tickets are moving to New Feature issue type, how to add a new field. I think we can't add it on new feature as mandatory field. It will affect new feature tickets while creating. Could you please suggest if you have any thoughts.
Hi @Lakshmi CH
You could:
For the last bullet point you will likely require an app which can provide scripting capabilities or automative actions.
You'd also need a trigger - for example if you're modifying the issue type of the issue to "New Feature" this could be the trigger - or if you've creating a new issue linked to the "Requirements Gathering" issue, that could be the trigger :)
But this method ensures the date is added automatically, rather than reliant on manual process.
If this sounds of interest, let us know and we can suggest some methods of achieving this.
Ste
@Ste Wright, we have script runner.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Lakshmi CH
You should be able to achieve this with a Listener - see more on how to create those on this page from their Knowledge Base :)
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Laksmi,
Is there a set value for a field that needs to be added? Could you do that dynamically? Or does the user have to input the value in the field during the move?
You could make the field required using a Field Configuration for the New Feature issue type.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @John Funk ,
the requirement is , When issue type Requirements Gathering tickets are moving to New Feature issue type, we wants to capture the date when the ticket is moved from one issue type to another issues, so while moving we need add new field called Requirements Gathering Transition Date.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you have already created the new field, simply add a Post Function to the transition in your workflow to populate that field.
Or you can do it with an Automation rule.
But create the field first. ;-)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@John Funk, Thank you for your quick responses. The exact question is,
For MD project tickets, when Type = Requirements Gathering is updated to Type = New Feature, we add/write a new Requirements Gathering Transition Date field (with timestamp to hours) to the date of the transition.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So in that case you would create an Automation Rule for Issue Moved trigger.
And set the Requirements Gathering Transition Date field to a value of now()
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.