JIRA Cability and best approach

[Ashutosh Kulkarni]

Hello Experts,

I need suggestion on approach to handle below requirement in JIRA effectively. ( Planned to use JIRA Cloud software ).

Project has requirement to use JIRA from day1 of project i.e. right from requirement gathering, HLD (High Level Design), LLD (Low Level Design), Development, Deployment etc. till final go-live.

What is intended to happen or required in JIRA is complete traceability is needed in JIRA for all complete phase of Project.

Planned JIRA users are around 100 / 150. Project initial team members would be around 50 and slowly as the Testing phase initiates (i.e. SIT and UAT), more team members, 3 PP and Client might also get involved in Testing and thus JIRA will also be used for Testing  / Test-Cases, Defects, tracking, dashboards, reporting  etc.

Given this as a requirement - can you please suggest Optimum way to handle this in JIRA and how should one design this requirement in JIRA.

Any Suggestion will be helpful for understanding. Thanks for your time.

[John Funk]

Hi @Ashutosh Kulkarni  - I don't see anything out of the ordinary with this one. 

Just create your project and your workflow as you want it. What would the different Issue Types be and do that have different workflows associated with them?

[Ashutosh Kulkarni]

Thanks John.

To understand this better, below is my understanding on suggestion :-

1. Create a Project with Different Issue Types e.g. Requirements, HLD,  LLD etc.

2. Create Workflows for each issue types in customized patterns as per requirement initially and later can be modified.

3. So overall only One JIRA Project (Classic) will serve the purpose.

If the Above understanding is right, I have one more question further :-

4. Assuming Project progress happens and post development - project lands in Unit testing (to be recorded against each requirement), how do we related to requirement ID.

5. Same is the question for SIT (System Integration phase ) and UAT (User acceptance Phase).

So Basically I am looking for Traceability throught right from  a Requirement ID to UAT phase - how can can be created using some Primary / Standard or Customized Columns is my question for complete Traceability.

.

Thanks in Advance for your time and inputs.

[John Funk]

Yes, you are correct on your steps 1-3 above.  :-)

For the others, I would create a Custom Field for each of those values that you want to capture, with a dropdown where applicable. You are not going to be able to run metrics very well if you do that, though.

The other option is to extend your workflow, or create an additional workflow that uses each of those as a status in the workflow. Then you could capture when and if an issue moves into each status. 

[Ashutosh Kulkarni]

Thanks again John. 

So basically, for the point #4 and #5 stated above, 2 options below :-

1. Create Custom field for tracking again requirement ID's with drop down and information is captured in Custom field, however I understand there are some limitations for custom field.

2. To take care in Workflow itself - which would mean have an extended workflow and capture details / sub-details in the " Status " of Workflow which will capture information in standard field pattern and will give flexibility to run queries or dashboard or reporting.

So to Summarize :- Right from Requirement to UAT phase of Project - this entire SDLC can (or rather should) be handled in Single JIRA Classic Project with workflow and transitions and if needed introduce Custom fields to capture more information and complete Traceability.

Let me know in case you have experienced / faced and limitations in this approach OR have any learning which I can take care, if any - this would be of great help.

Do please let me know in case of any disconnect in understanding.

[John Funk]

Yes you are on the right track. I would suggest you proceed with option 2.

[Ashutosh Kulkarni]

Thanks for your time and inputs John.