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

Editing epic label

Рустам Шехмаметьев

How jira developers decided to make this auto incrementing labels?

I don't need it. How can I turn them off?

PS When I deleted the epic with "MF-1" label and created new one, it got the "MF-2". LoL? How can it be "MF-2", if it is only one epic I have? This is not understandable.

Accepted answers

Nic Brough -Adaptavist-

Welcome to the Atlassian Community!

I think there might be a problem with some of the words here. Plain English and English-Jira-speak are not quite the same thing.

I think that when you are looking at the MF-1 and MF-2 things, you are not talking about Jira's "labels", you are talking about the issue key. Each issue is a unique object with a unique key that is based on the project (MF) and a sequence that makes it unique within that project.

A "label" in Jira-speak is a bit of text that you put on an issue to try to group it with other related issues. Same thing as a "tag" here in the Community (look to the right, you'll see the tags "cloud", "jira-software" and "jira-software-cloud" for this conversation, unless someone has edited them more recently than I wrote this)

So, assuming MF-1 and MF-2 are really the issue key, not lables/tags, then yes, Jira is working as intended.

An Epic is an issue in a project. It therefore gets a unique key based on the project and a sequence number. As you create more, the sequence number simply increases. The number you have, whether deleted or not, Jira simply generates the next number and allocates it to the new issue.

This shouldn't be a problem for you - best case, you can look at numbers for a bit of info on when they were created. Most simple case, it's just a unique ID for the issue (Epic) and you don't care about the number.

All comments

Nic Brough -Adaptavist-

Welcome to the Atlassian Community!

I think there might be a problem with some of the words here. Plain English and English-Jira-speak are not quite the same thing.

So, assuming MF-1 and MF-2 are really the issue key, not lables/tags, then yes, Jira is working as intended.

Рустам Шехмаметьев

Uniqueness is ok for existing epics. But it should not count epics I deleted. Deleted. Deleted means deleted. Not removed or archived or detached.
There is the "Delete" button which have own reminder that "You're about to permanently delete this issue, its comments and attachments, and all of its data."
When I'm looking at this lonely epic tagged "MF-2" I think: "Stop, there is my first one?".
If it is as you said "Jira is working as intended" I just want to hide this tags. Jira tags are confusing.

Nic Brough -Adaptavist-

You are still confusing keys with tags or labels.

The issue key is not a label or a tag, it is a unique identifier for an issue and it is a core function too. Whether the issue still exists is an irrelevance, there was or is an issue uniquely identified by that key.

You probably do not want to hide this ID either. It's the unique identifier for an issue and it is used for finding, reporting and updating issues. There's not a lot of point in tracking issues if you can't uniquely identify them.

This brings me to the obvious question - why do you want to hide this? What problem would hiding the key solve?

Рустам Шехмаметьев

Just say that Jira doesn't have an opportunity to hide this auto-generated info and I will accept the answer.

Parveen Vats

hi Pyctam,

Can you advise me how you have created EPIC serial numbers like JS-1, JS-2, JS-3.... ?
Pl help

Thanks

Parveen

Nic Brough -Adaptavist-

They created a project with a key of JS and then created epics in it.

The key is the unique identifier of an issue.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud