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

Change the custom field to store the "Flagged" information

Bernd

Is there a way to define another custom field to be used for storing the "Flagged" information of an issue?

Background:

We already had (long before the agile things got added via a Jira update) a custom field called "Flagged" which contains business related information. After enabling scrum boards for this project the "Flag an issue" feature is using "our" custom field instead of a separate one causing business related information to be set by mistake. Renaming the "Flagged" field and adding a new one did not solve this issue.

Accepted answers

John Funk

It’s never good to change the name of or otherwise mess with the structure of system fields.

You are better off creating a new custom field for your purposes and migrating the data to that field.

All comments

John Funk

It’s never good to change the name of or otherwise mess with the structure of system fields.

You are better off creating a new custom field for your purposes and migrating the data to that field.

Bernd

"Flagged" is a system field? I thought that we added it in our first used Jira version 4.3.4 as a custom field and that an agile update just did not add a related system field.

John Funk

Well, maybe not a "system" field by name - but it is treated that way. It should have the designation of "LOCKED" beside it.

In other words, the Jira system is looking at that particular field when it makes certain changes in the system.

Welcome!

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

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server