nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Copying status from Custom Field does not update transitions for copied status

unknown

Hey there,

I am creating a "More info needed" status in my workflow. From this status I need the issue to return to the status that it was previously in before it go sent to "More info needed" so that when a user replies to the info, it goes neatly back to the status it was in for processing.

I am achieving most of this by storing the previous status in a custom field. When the issue is given more info it's sent back to the "Backlog" status, at which point I use a post function to update the status field from my custom field, so its status gets updated.

This works mostly, the status gets updated accordingly, however the actions from that status do not, they retain the transitions allowed on the "Backlog" status only and the transitions for the status stored in the custom field do not get applied even though he status does.

Is there any post functions that make sure that the correct transitions are being applied for the status that is being applied? Or s there an easier way to achieve it, it al feels a little convoluted! Maybe others use a "More info needed" status differently?

Thanks a mil!

Lisa

Accepted answers

Matt Doar_tzgiej

You can store the name of the previous status. Then define a transition from Needs More Info to each of the possible previous states. Use a condition to only show one of these transitions based on the value in the custom field Previous Status. That way only one transition will be see and it will go back to the correct previous status. As Nic says, don't directly update the standard Status field.

But you say you are going from Needs More Info to "Backlog" status, whatever that is. Perhaps you mean the backlog on an Agile board?

All comments

Alexey Matveev

I guess you would need to put the Value Field conditions for all transitions. In the conditions you would compare the value of your custom field to the status to which each transition leads. For example. Let 's say you are in the "Backlog" status and you have two transitions from the status: one transition to In Progress status and the other one to In Testing status. Then for each transitions you would add a condition like this

For the tranistion which leads to the In Progress status: previousStatusCustomField = "In progress"

For the transition which lead to the In Testing status: previousStatusCustomField = "In testing".

It would hide unnecessary transactions.

Nic Brough -Adaptavist-

This sounds like you are using a function to copy status from a field into the status "field".

Never do this. Status is NOT a field, it is an indicator of position in the workflow. You can't change status like this. You must use transitions to change status. There are add-ons that can help you with automated transitions.

If you are copying, then I would recommend removing that function immediately to stop the damage it is doing. Then we can look at repairing it.

unknown

Will look into that. I guess warnings should be put in place if it's that much of a bad thing to do eek! We are only getting our workflows set up before launch though, so no damage is done! Thanks for your answer.

unknown

Thank you for your suggestions!

Matt Doar_tzgiej

But you say you are going from Needs More Info to "Backlog" status, whatever that is. Perhaps you mean the backlog on an Agile board?

unknown

Thanks for your help Matt, much obliged!

unknown

Let me try to think out of the box, because it sounds like you is trying to use the jira in an awkward manner .

As i understand your problem. You want to be able to change status from lets says In progress, In testing, Being validated , and move them to "Need more Information" and return to the step from which it came.

Like In progress -> Need more information" -> (automatically) In Progress then -> In testing -> Maybe " need more information" and back , or maybe just directly to Being validated ?

I suspect the reason for this behavior is because you want to be able to identify the " need information" and make sure they are answered before they continue in the other flow ?

Maybe you have separate people who needs to react on these issues and maybe you want to keep the board clean from the "need more info" parts until they are answered?

If you can elaborate on what you are trying to do I think we would be able to find a better solution thatn to change statuses.

E.g. Use a custom field to indicate I need more info.

Add a filter on your flow board (In progress -> In Testing -> Being validated) which only shows the once that are not in need of more info.

Then make a filter to show all the "Need more info" and add it on peoples dashboard so they will see it.

If the person who needs more info also tags the person (Another type of custom field or in the comments) then this guy should be automaticly notified.

I hope my answers will inspire you so that you can make the right choice

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

workflow

status