JIRA Cability and best approach

Question

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.

Ashutosh Kulkarni · Answer

Thanks for your time and inputs John.

John Funk · Answer

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

Ashutosh Kulkarni · Answer

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.