Project Keys

[Ramiro Vallina]

Hello! Ramiro from Argentina. 

Could I have sequential project keys for each issue?

For example, for my Project MARS

EPIC= MARS-1

User Story=  MARS-1.1
                SubTask= MARS-1.1.1
                SubTask= MARS-1.1.2
User Story=   MARS-1.2
                SubTask= MARS-1.2.1
                SubTask= MARS-1.2.2
                SubTask= MARS-1.2.3

EPIC= MARS-2
User Story= MARS-2.1
                 SubTask= MARS-2.1.1

I think it's a good way to be organized with my development team

Thanksss!!

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

Simple answer is "no".  Jira's issue keys are a simple <project key>-<sequence>

In a lot of places Jira will display sub-tasks as part of their parent though, so at least you get to see "ABC-123 / ABC-234" where it matters.

[Ramiro Vallina]

Thank you Nic! That display is automaticly or i need to configure it?

[Dwight Holman]

Adding to Nic's answer - the project key can include alpha-numeric characters. You can create project keys like MARS1, and MARS2 which would produce issue sequences

• MARS1
  • MARS1-1
  • MARS1-2
  • ...
• MARS2
  • MARS2-1
  • MARS2-2
  • ...

Generally shorter project keys are better IMHO, but this is an option.

[Nic Brough -Adaptavist-]

But that would move all your stories up to the project level, which makes them useless.

[Ramiro Vallina]

It would be very interesting to have a key structure that is

<ProjectName><IssueType><Sequential>

That would allow my work to be organized better, especially in integrations with GitHub or GitLab.

[Nic Brough -Adaptavist-]

That's actually one of the things Jira was written to get away from - compounded unique keys are clumsy legacy structures that cause more problems than they solve.  Just include the issue type in your reporting!