Can I retain approvers when moving to a separate status?

[sergio.peschiera]

I have a status in which certain approvals are necessary to be able to progress the ticket forward. In this workflow, I also have a 'more information needed' status which we use to request for more information from the requestor. However, the problem with this is that when transitioning a ticket to this status, we lose all current approvals. Is there a way to keep approvals when transitioning to a different status?

[Matthew Rochman]

Hi @sergio.peschiera and others,

I have exactly the same issue:

However, we may have to go back and forth between A and a third status, C, in order to obtain more information. If I require 4 approvals to get from A to B and I have 2 but need more information, these 2 are lost when I move to C. Is it possible to keep these approvals when the status is moved to C?

Seemed to be some confusion from other posters. If a step requires three approvals and so far you have 1 of the 3 approvals, then it goes to a status "waiting for more info" or similar, then moves back to the approving status, it shows up as "awaiting 3 approvals". That 1 person who already approved needs to do it again as the registration of their approval is lost when it goes to the 'more info needed' status. 

How can the pre-existing approvals be retained if it goes back and forth between a 'more info' status? 

[sergio.peschiera]

I have a condition that requires approvers to move from one status to another. Let's say, if approval is granted, the ticket has to move from A to B. However, we may have to go back and forth between A and a third status, C, in order to obtain more information. If I require 4 approvals to get from A to B and I have 2 but need more information, these 2 are lost when I move to C. Is it possible to keep these approvals when the status is moved to C?

[Bharathi]

Hi @sergio.peschiera,

Please make sure that when you transition your issue through 'more information needed' status, you are accepting information on the necessary new fields and not clearing out the values of the other existing fields. There is some issue in that transition which clears out existing field values which makes to lose all current approvals.

Or if you load the information of all approvals on the same field, make sure that the new value gets appended to the existing value in this transition.

Hope this helps!

Thanks!

[sergio.peschiera]

I have a condition that requires approvers to move from one status to another. Let's say, if approval is granted, the ticket has to move from A to B. However, we may have to go back and forth between A and a third status, C, in order to obtain more information. If I require 4 approvals to get from A to B and I have 2 but need more information, these 2 are lost when I move to C. Is it possible to keep these approvals when the status is moved to C?

It's an approver field, not sure how not to lose information there.

[Aditya Sastry]

How does the approval get lost? Ok, I believe 

I would suggest to add the approver name to an user picker field maybe "Approved by" as soon as they provide the approval through post function. This way the details of users that have approved remains stored and you don't loose it even if it is transitioned to another status.

Let me know if you need more information.

Thanks,
Aditya

[sergio.peschiera]

I guess this would work but it's not a great UX as it has to go through a field and the trnasition wouldn't be automatic. I feel there has to be another way

[padraik]

What do you mean that you lose all current approvals?

How are you storing the approvals?  Are they not each a user picker custom field?

[sergio.peschiera]

See the screenshot in my comment above, they are stored through the approver feature in JIRA