Hide Key ID from Project

[Shaun Delorez]

Hello. We are just starting to use Jira Software for a development project. We see the project key is created when the project is started. It also appears for each Story, Issue, Task, etc we make.

For example, we make a project called New Website with a key "WEB". All items we create in the project are incremented "WEB-1", "WEB-2", and so forth.
I understand from other discussions that these can only moderately be customized. What we want to do is have different IDs for each of our stories.

For example, we make a story "Build Database", and we would want an ID called "DB-1, DB-2, etc".  Then another story would be called "WebUI" with IDs called "W-1, W2, etc".

Is this possible? I gather that we can create a custom field for the project. But even after doing so, we still see the project key in the item list.

I would greatly appreciate any other opinions or solution suggestions for this.

[Nic Brough -Adaptavist-]

There is no way to do this as described - the project key is an integral part of the issue key, and the whole of Jira and its applcations and apps work on the project key being the first part of the issue key.

The closest you will get is to create projects down component lines - so a project for Web, and other one for WEBUI, a third for DB and so-on.  This is how some people work though, and it can work really well, especially if you use boards for teams instead of tying them to projects.

The issue key is too important to "hide", it's the crux of most of what Jira does.

[Shaun Delorez]

Thanks for the responses. 

What we're looking for is to have identifiers relative to their Epic.  So, epic 1 has issues 1,2,3 and so forth. It would be nice for the identifier to be labeled as E1-1, E1-2, E1-3...and so forth.

Then the other epic would be E2-1.  You get the idea. 
All I can make happen so far is a single series of IDs based on the project key, and they're numbered in the order they are typed in. The number can't be edited or reordered later.

This is a visual presentation thing for us. We would want to say "hey did you get any progress on E2-56?"

Hopefully my profile explains well enough:  I AM new here. I've got about 3 college classes of generic development education under my belt, and I've used Jira long enough to know how to spell it. I do appreciate the help I get from the community, and I excuse my lack of experience ahead of time. 

[Nic Brough -Adaptavist-]

This would make your Epics represent things we would normally see as projects in Jira.  This is also not at all a bad idea.  Epic = giant thing too big to tackle alone.  Project = big pile of things that add up to provide something.  They're not that far apart.

I'd still try to break up your work along project lines, and then you can use Epics for what they're really for - grouping together things (often cross-project) that need considering together.

[Fazila Ashraf]

Hi @Shaun Delorez 

What is the reason for having different key for different type of tickets?

If having different keys are very important, Could you use different jira projects for those different types? Note that the jira agile boards can pull the tickets from multiple projects.