Hello.
To optimize the work, you need to change the fields for bugs in Jira.
(In particular, the 'Description' field to change by the customer field). I need to create a new customer field and hide the old one, but then the data from the field of previously introduced bugs is lost.
A problem arose about how to copy the value of an old field to a new one.
Please tell me how to do this.
Hi,
That's not directly possible. All new issues, including sub tasks, always take the first status in the workflow.
The only way around this would be to use some kind of automation add-on to walk the issue through the appropriate transitions to get to the right status you're looking for.
This is because Status is not an editable field, and cannot be specified as such. Its a construct of the workflow and the workflow always starts at the top.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Not familiar with JMWE, but I think there are possibly things you can do with Suite Utilities for Jira (an add-on I highly recommend) or Script runner as @Tinker Fadoua mentioned.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No app will allow you to change the issue status without transitioning the issue, especially on Jira Cloud.
As Josh mentioned, you need to transition the issue to its desired status. For that, you can use the Transition Issue post function on the Create transition of subtasks to walk the subtask through the réquipée transitions to the desired status, using the conditional execution feature of the post function to only run the required transitions. You could even create hidden transitions that would go from the initial status directly to each possible status, so that you’ll need to transition the subtask only once.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@David Fischerthe user is asking for the change at the sub-task level not the parent. I was able to make the sub-task go to in-progress automatically when the parent ticket is approved using "Create on transition" add-on.
Best,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
"Create on transition" add-on is not supported by cloud. so it appears there is no solution other than change the status manually.
Thanks anyway
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Michael Cohenunfortunately they don't have it for Cloud which I checked and told you earlier. Try the ScritpRunner plugin.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Michael CohenI know for fact that JIRA out of the box doesn't have lot of post functions. I just checked the one add-on that has lot of features is "Create on Transition" from Bob Swift, unfortunately is not available for Cloud users.
May be ScriptRunner which is available for Cloud users.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.