Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Utilizing fix versions and releases for hardware product development

Nil Ister
Contributor
June 24, 2019

This question is about utilizing Jira, specifically fix versions, for a hardware product. 

Let's say our product is a thermos and each sub-component (lid, o-ring, etc.) goes through prototyping, testing, and manufacturing stages. These stages will be the fix versions (only three fix versions for the thermos to be built).

Each component has an epic that looks at tasks related to that component. Tasks and sub-tasks are tagged with the corresponding fix versions. So now we populated numerous tickets under fix versions. As I mentioned, imagine that I only have three fix versions since at the end all of the components need to be released to make the thermos.

If I have a portfolio plan for each component (I know that I can have one with all components but say I do it this way) and if I release issues that are in prototyping stage for the "lid", what would happen to the rest of the tickets in the "prototyping" fix version?Would they remain in the version as "unreleased" and the "prototyping" version would not be released? Would it be better if I create fix versions called "prototyping - lid", "prototyping - x component", "testing - lid", etc.?

Sorry for the complicated explanation. Also, please feel free to share your opinion on hardware product development using Jira in general, I would really appreciate it.

1 answer

0 votes
Alex MyLastName
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 19, 2025

Hello.

I'm faced with a similar challenge. How did you resolve it?

 

Suggest an answer

Log in or Sign up to answer