Refer "people" in other fields name

Question

Hi all!

We are working with Jira to describe problems and record measurements to solve the problems. Part of our workflow is, that the team mates responsible for diffenrent tasks have to be chosen by the reporter. Later on the team mates have to approve parts of the problem desciption or that they performed the measurement they were responsible for.

No comes the problem:

At the moment the reporter selects the needed team mates in the configured "people" field.

The approval is done by choosing "approved" or "not approved" in a drop down field. In the field name at the moment is only "person 1" or "person 2" statet. What I would like to configure is, that the team mates name is automatically added to the field name.

Thereby every team mate knows where to add his/her approval. And when exporting the issue it would be cleare who was responsible for this steps.

I hope you have some ideas to solve my problem.

Thanks in advance!

Diana

Robert DaSilva_a432as · Answer

@diana_pohle Let me know how it goes! There may be some particulars you need to massage based on your specific instance and requirements.

diana_pohle · Answer

Hi @Robert DaSilva ,

Thanks for your answer. I already thought that it wouldn't be as easy as I had imagined. ;-)

As we already have a clone of our project specifically for testing, I will try your suggestion there.

Robert DaSilva_a432as · Answer

Hi @diana_pohle , it is not possible to modify the display name of a custom field in the way you're aiming to accomplish.

If I understand the problem correctly:

* You have tickets that capture problems that need to be resolved
* There is a "People" multi-user picker custom field which contains a list of users who can provide approval on the solution
* You want to capture which individuals provide approval on the ticket in a way that can be exported for audit purposes

In order to accomplish this, I think there will need to be a number of changes to the issue workflow in Jira, the custom fields, and potentially some Jira Automation rules. Here's my thoughts:

* Create a new multi-user picker custom field called "Approval Provided By", and add this to the VIEW screen for the screen scheme that applies to the tickets in question.* Adding this to the VIEW screen prevents this custom field from being edited by anyone, as it should only be modified by the workflow, detailed below.

* Update the issue's workflow to add a new self-transition called "Approve".* Add a "User Is In Custom field" condition to this transition such that only users in the "People" multi-user picker custom field can execute the transition.
* Add an "Update Issue Custom Field" post-function to this transition, which appends the current user to the "Approval Provided By" multi-user picker custom field.
* Optionally, update the transition where this approval needs to have been provided to require the "Approval Provided By" custom field be not empty, to require that at least one approval has been provided before it can transition forward.

* Optionally, create a new Jira Automation rule to create a new comment that calls out the person who provided the approval.

This should capture those who have provided the approval in a new custom field, and the details of this custom field will be exported with the issue.

As this is a pretty significant change, I would strongly recommend testing this change in a sandbox or testing project before you apply this to your production environment.