Resolving the Jira Inheritance Issue
Time is a precious and valuable resource, especially as it applies to software development projects!
For this reason, we recently saved one of our Credit Union clients time and money by implementing a solution to circumvent manual data entry by their testing team.
A major issue expressed by this client was the fact that their testers were spending too much time manually typing in the same values as the parent issue such as: Epic Link, Sprint Value, Release, Priority, etc.
This issue was classified by our team as a ‘Jira Inheritance Issue’, and we needed to find the most cost-effective and relevant solution to resolve the client’s problem.
A little background on the project:
Our client needed assistance in developing a testing strategy that would allow a previously purchased tool (Jira) – which was not commonly understood or leveraged by the testing team – visibility to the project requirements as well as embracing of Agile processes.
Olenick’s team worked with the client to gather their practices and preferences on documentation of findings in their spreadsheets, then started defining and building a Jira project with hierarchy for issue types and workflows, all leveraging custom fields of the Jira Software. Our team made sure to provide process consulting to ensure the best practices were reflected in Jira, and the work was demonstrated to the client.
The client gained a powerful built-from-scratch Jira project that enabled tracking of their work without all the manual inputs previously required by their old model – they were excited to begin their new project journey, now with a tool to support their efforts! We also helped the client take significant steps to doing effective Test Tracking using the Jira Add-on “Zephyr“, and Test Execution and Dashboard building using the Jira built-in Metrics.
After some research, the team decided to install another addition to their Jira environment, the “MISC” Jira Add-on. We demonstrated that if an issue type has a child linked to it, this one would automatically inherit the values from its parent without the manual steps. We also showed them a onetime step that resolved their concern on Post functions being added to the issue types workflows. We also eliminated any sort of human error that could occur in the future if a tester forgot to enter the parent link, so that new created issue types would not inherit anything.
The client was impressed with our training, documentation, and demonstration of the new process. They were also impressed by the processes ability to prevent human errors plus save time and effort.
We helped our client encourage the adoption of their new Jira project and guided them by providing our best practices and trainings on Atlassian tools and the inheritance add-on.
Our successful implementation of the project included a teaching experience where people went from not knowing anything related to Jira/Zephyr/Atlassian to becoming extremely comfortable and knowledgeable with these tools. The Olenick team is proud to have not only developed a custom solution to our client’s problem, but also to have delivered training for their in-house testing team to set them up for future success.