Obtain Field Value from different dates

[Garth Smitman]

We use jira to track work and to record "requirements".

We assign a requirement to the Version.

Sadly, we tend to need to maintain the same Issue Key for a Requirement across multiple versions. This generally works, until I have the following:

Version 2.0 is in the field (Requirements Frozen on 4/1/2022)

Version 3.0 is in the field (Requirements updated and Frozen on 4/1/2023)

Version 3.1 is about to release (Requirements updated on 5/31/2023)

Version 3.2 is under development (Waiting to update, information is known)

We have updated the description / Acceptance Criteria on the Requirement to reflect the needs of Version 3.1. 

We are ready to Test for Version 3.2, but have held off on the update to the Requirement because Version 3.1 is not release ready.

We encounter a Bug in Version 2.0 and need to make a correction. 

In this nightmare of refusing to clone issues and assign them to the proper releases, is there a way / method to extract the information which existed for this Requirement back in Version 2.0? Version 3.0? 

Is there a way to make the updates for Version 3.2, but still pull the Version 3.1 data?

Hopeful,

-gs

[Mikael Sandberg · Accepted solution]

The short answer is no, since Jira do not version control an issue, what you are trying to achieve is not possible in Jira. In a previous life we had a similar set up and used Jama Software since that allows you to version control your requirements, and then link them to your issues in Jira.

[Garth Smitman]

I suspected as much. 

I'd like to encourage the Testing (um, Verification and Validation group is our term - if you haven't guessed, we are in a regulated industry) to embrace Cloning and Linking, so that the 'Version' of the issue / ticket is moot - the FixVersion or Product Version or similar attribute is the important piece. 

Thanks for the quick response!

-gs