How to adjust the field name according to status

[Tim Straub]

Hi,

we have to create a workflow for a single project that contains predefined field names for fields. These field names are predefined for an official certified workflow and cannot be changed.

Almost all of these fields already exist in Jira, but are called differently there.
For example, the field "assignee" would only have to be changed to "Approver" for this project if it has a certain status in the workflow.

Let's say:

1. A "reporter" (in jira "author") opens a task.
2. The first person ("assignee" in Jira) takes this issue.
3. If this really needs to be escalated, an "approver" (in jira the next "assignee") will take care of this issue. If there is an "approver" assigned the field name should state "Approver".

Is there a way to display the field names (what the user sees) differently depending on the status or transition, dynamically?

Thank you.

Tim

[Nic Brough -Adaptavist- · Accepted solution]

There's no way to do this, and it does not make a lot of sense either.  Field names should be consistent, not state dependent, or you'll just confuse your users.

Also, imagine any you have two issues, one in one status so that "assignee" comes out as "assignee", and one in another so you want "approver" - this is nonsense the instant you look at these issues in the navigator, or try to do any reporting.  Which name do you display?

[Tim Straub]

Hi Nic,

the technical field name inside jira should not be changed. Just the text shown to the user to meet the official requirements.

Regards

Tim

[Nic Brough -Adaptavist-]

That's exactly what would be utter nonsense to your users.  Having more than one name for a field does not work for them, or on the back end.

[Tim Straub]

So for such a requirement I should prefer using custom fields?

[Nic Brough -Adaptavist-]

Absolutely.  In the case you describe, I would use assignee as intended, and have a user picker for "approver".  I would probably think about setting a script to re-assign the issue to the approver when they need to take action, and then on to someone else when they approve

[Tim Straub]

I wanted to use as few custom fields as possible and thought there would be something without additional fields in the database.
What would you run the script with? Which free option do you recommend?

[Joe Pitt]

Be careful when using a free, probably unsupported, plugin. They may stop being available. I've had it happen. 

[Tim Straub]

Well, I'd like to ask my question differently.
Currently I only know that scripts can be used with plugins like Script Runner.
Is there an alternative to the paid tools, if so which?
After the current price increase on Atlassian products, a new paid tool does not go down so well in our company.

[Nic Brough -Adaptavist-]

Not really, the paid tools are the ones that have the money in order to pay for proper development and testing.