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

Project key/Issue naming conventions

Gareth Ford

Hi all,

I think I know the answer to the following question but figured it would be sensible to ask before I forget about it and move on...

We are looking to log all of our Incident and Service Request issues in the same project (and most likely Change and Problem..). From what I have read, there is no way to differentiate these issues from one another solely by their naming convention (i.e. INC, REQ, PRB etc) as all of them are given their name based of the Project Key within which they are logged.
Am I correct in thinking this and therefore that the only way to differentiate between the differing issue types from this perspective is to create different Projects for each differing Issue Type...?

Hopefully this makes sense!

Thanks

Accepted answers

Alexey Matveev

Yes, you are right. If all issues are in the same project than you can differentiate them by issue types. Or you could move them to different projects.

All comments

Alexey Matveev

Yes, you are right. If all issues are in the same project than you can differentiate them by issue types. Or you could move them to different projects.

Gareth Ford

Thanks for responding so quickly, Alexey. When you say we can differentiate, that is only by logging them as different issue types - correct?

We are not able to change the prefix of the ticket based on Issue Type within the same project (i.e. they will always begin with the same key whatever type they are)?

Alexey Matveev

That is right you need to log them as different issue types. Their prefix will be the same (the key of the project)

Gareth Ford

Thanks Alexey

Welcome!

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

Quick Links

Find more posts tagged with

jira-service-desk