Can i have different Story Names within a single project

Question

I need to identify Development and Test stories within a single project.

Is it possible to create stories within a project with different naming convention.

Currently :

Say projectname = "ABC"

Story names will be ABC-1 ; ABC-2...and so on.

What i want to do is :

Project : ABC

Epic Names : ABC -1

Development Story name : ABC_Dev-1

Test Story name : ABC_Test-1

Jack Brickey · Answer

Option 1: I don't know why it would be difficult to identify test from dev. This could easily be done by using different Issuetypes or a custom field.

Option 2: the issue here is that if the sub-tasks do not complete in the same sprint then the entire story is returned to the backlog/next sprint so you will have a hard time tracking work done in a sprint.

My recommendation is Option 1 w/ either different Issuetypes (Develop, Test) or a custom field associated w/ the default Task Issuetype.

Sharad Patel · Answer

@Jack Brickey ,

Thank You.

Why i need to do this is to identify Testing Stories from the Dev Stories for traceability purpose.

For a project there would be Epic , which will contain Multiple Stories.

(Say Project name = ABC ; EPIC name = ABC-1. Stories will also follow same naming , story name = ABC 2.)

Now these stories are Primarily for Development to start working on them.

The Test team will have to generate artifacts for the Story testing and i want to tie these artifacts in JIRA to specific stories. If i do that i will have 2 options :

Option 1:

I Create Testing Stories and assign them to the relevant Epic . Now i will have as many Testing stories as Development. And Yet the naming will still be ABC-n...). It will be very difficult to identify Testing stories or trace the testing stories to the Dev Stories.

Option 2 :

I create Testing Tasks / Sub Tasks for each Dev Story to create Testing Artifacts. This gives me a better traceability of each story having testing artifacts ready. But the Naming of these task/sub-task will still be ABC-n... and so on. And the fact that A story can have task as well as sub-task , makes things little bit complicated for me to have a complete Traceability.

And therefore i wanted to know if i can name my Testing Stories differently , then while running a report for traceability , i can just filter out the Testing Stories.

I dont know if this would help. I may be over complicating things here since i am very new to JIRA. But please suggest if i can tackle this problem with any "out of the box" feature in JIRA.

Thank You.

Sharad.

Jack Brickey · Answer

True, but why do you need the key to be named uniquely vs. just using issuetype? It seems to me you are trying to combine issue key with issue type into a single field?