Is it possible to have 2 separate autoincrement-index? One for Epics and Stories and the other for the rest (normal Tickets) ?

[Phillip Lüdeling]

What we would like to do is to further separate Stories from the Bug-Tickets.

issue-type: Epics and Stories
PROJ_US-1, PROJ_US-2, ...

issue-type: Bugs, everything else
PROJ-1, PROJ-2, ...

I guess a script is needed here. Can anyone point us in the right direction?
Much appreciated.

[Danielle Zhu · Accepted solution]

Thanks for the clarification. JIRA keeps a single issue counter (pcounter) for each project and increments that for the next available issue key. It sounds like you want to change the way JIRA constructs an issue key. Maybe some JIRA developers can chime in here.

[Danielle Zhu]

You can separate epics and stories from the rest using GreenHopper Context. Instead of using the Default context, you can create new contexts e.g. "Epics and Stories Only", "Bugs etc." In the new context, just define different filtering criteria based on Issue Type. Hope this is what you are looking for.

[Phillip Lüdeling]

Thank you for your quick response. But this is not quite the feature needed.

Our Problem is:
UserStories and Bugs are created throughout project's Lifetime.
The main issue-id (running index from 1 to n) is disturbed in order, when bugs are created.

So we have:
(Story) (Bug) (Story) (Story)
PROJ-1, PROJ-2, PROJ-3, PROJ-4

What we want to achieve:
(Story) (Bug) (Story) (Story)
PROJ_US-1, PROJ-1, PROJ_US-2, PROJ_US-3

[Phillip Lüdeling]

This might be a more general jira question i'm afraid. Maybe we should just use 2 different projects.

[Danielle Zhu]

yeah, that may very well be your solution.