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: * A "reporter" (in jira "author") opens a task. * The first person ("assignee" in Jira) takes this issue. * 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

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; } } }

How to adjust the field name according to status

unknown

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:

A "reporter" (in jira "author") opens a task.
The first person ("assignee" in Jira) takes this issue.
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

Accepted answers

Nic Brough -Adaptavist-

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?

All comments

Nic Brough -Adaptavist-

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.

unknown

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.

unknown

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

unknown

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.

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server