Is it bad form to use 'Fix Versions' to track the maturity of an idea to technology development?

[Paul Scarlett]

Is it bad form to use a Fix Version to simply name the end of a maturity phase in developing an idea through:

• to a clear problem definition with stakeholders - Fix Version A
• to a set of use cases & requirements - Fix Version B
• to a set of alternative system concepts - Fix Version C
• to the selection of the best concept - Fix Version D
• to the identification of the technologies (new, carried over or exploited) - Fix Version E
• to the release of those technologies/ applications - Fix Version F 

[Bill Sheboy · Accepted solution]

Hi @Paul Scarlett 

As a disclaimer, I am just another Jira user, and not employed by Atlassian or any marketplace vendor.  With that out of the way...

Jira is just a tool, and although there are some better (and worse) ways of using it, you can decide how you use the features, and accept what happens.  Releases / versions help solve a specific need, and if you use them for something else that could cause confusion down the road for your teams.

As you are describing a flow from concept-to-cash, including ideation, have you looked at Jira Product Discovery to help with that type of high-level and road-mapping flow?  Please look here for more information: https://www.atlassian.com/software/jira/product-discovery

Kind regards,
Bill

[Paul Scarlett]

Thanks for that Bill, I'll take a look.

[Léo Dumortier]

Hello,

Nothing is bad if it's answering to your needs !

But why not use a specific Workflow where you have statuses matching your list ?

It seems you're describing a "processus" , a "lifecycle"... So I'd say, use a workflow in my understanding.

[Paul Scarlett]

Thanks, Leo - will think on this further, after I've look at what Bill suggested looking at above.