Summary of functions affected by revisions restructure in R4J 4.5

Project Activation

Affected function

Behavior changed?

Notes

Affected function

Behavior changed?

Notes

  • Project Activation

Yes

Project activation will be immediate since revision history generation is removed.  

  • Project Deactivation

No

R4J v4.5 project deactivation will be as it was before upgrade. Deactivating a project does not delete revision history data.

Revision Cleanup

Affected function

Behavior changed?

Notes

Affected function

Behavior changed?

Notes

  • Deletion of old data (Cleanup Revisions Administration)

Yes

New entry in the Add-ons Administration page, allows Jira Administrators to delete unnecessary entries in the R4J revision tables.

The cleanup process will delete revisions for issues that are not in any tree and not in any baseline. Revisions of unchanged values will also be deleted. Please backup your data before executing the cleanup. 

  • Issue Deletion (Jira Delete)

No

Deleting an issue in Jira will delete revisions for issues that are not used in any baseline

  • Project Deletion (Jira Delete)

No

Deleting a project in Jira will delete revisions for all its issues that are not used in any other project’s baseline. The deleted project’s baselines will be deleted.

  • Remove issue in tree

No

Once an issue has been added to the tree, its revisions will be tracked further on.

If issue is removed in tree, revisions will still be tracked. The “Revisions Cleanup” process can clean this up if unwanted.

Revisions

Affected function

Behavior changed?

Notes

Affected function

Behavior changed?

Notes

  • Tree > Add existing issue

  • Tree > Create issue

  • Tree/Jira > Modify Issue

  • Tree > Reuse

  • Tree > ReqIF import

  • Scheduled adding of issues

  • R4J Excel Plugin > Import of issues

Yes

After a Jira Administrator executes the “Revisions Cleanup” process, revisions will only be tracked for issues that have been added to the tree. Once an issue has been added to the tree, its revision will be generated and tracked further on.

  • Tree > Issue Links

Yes

Issue links before v4.5 were never tracked in R4J revision history. For revisions v4.5 onwards, issue link changes (linking/unlinking) will show in the revisions.
Tip: If unwanted, please include Linked Issues in the field blacklist.

  • Tree > Issues from non-activated projects

Yes

Issues from non-activated projects before v4.5 were never generated with revision data which may cause missing items in baselining.

For revisions v4.5 onwards, any issue added to any requirements project tree regardless if it is activated or not will be generated with revisions to maintain consistency in data especially when baselining.

Baselines

Affected function

Behavior changed?

Notes

Affected function

Behavior changed?

Notes

  • Baseline Details

  • Baseline Comparison

  • Baseline List

No

R4J v4.5 will display baselines and baseline information as it was before upgrade. 

  • Baseline Delete

No

Revisions will be deleted for issues that no longer exist in Jira.

  • Baseline Create

Yes

Baseline creation will be a bit slower from R4J v4.5 since the complete generation of revision history data has been shifted here instead of during project activation.

Detail View

Affected function

Behavior changed?

Notes

Affected function

Behavior changed?

Notes

  • Revision section > Changesets

Yes

R4J v4.5 retains old revision data from lower versions while incorporating Jira history into new revision data. Old and new revisions may differ slightly in how revisions are created. Most noticeable is generation of revisions for Linked Issues which was not supported in lower versions.

Blacklisted fields will not be displayed in the Detail View and will not trigger a revision.

  • Revision Section > Suspect marks

Yes

R4J v4.5 tracks suspects through the R4J Suspect custom field which provides details on the changed issue and linked issue(s) affected. This information will show in the revision history.

Tip: If unwanted, please include R4J Suspect in the field blacklist.

  • Revision View/Compare

Yes

Revisions can still be compared between issues. For issues that do not have R4J revisions (never added to any R4J tree), only current field values can be compared. Additionally, because of the differences in how values are stored in R4J history vs the Jira history, formatting and display for some custom fields may differ between old R4J revision data and Jira value which affects revision comparison between old and new revisions.

Issue Revision and Comparison

Affected function

Behavior changed?

Notes

Affected function

Behavior changed?

Notes

  • Requirements > (General) Issue Comparison

  • Detail View > Issue Links (Review, Compare)

  • Suspect Report (Review, Compare)

Yes

Revisions can still be compared between issues. For issues that do not have R4J revisions (never added to any R4J tree), only current field values can be compared.

R4J Custom Fields

Affected function

Behavior changed?

Notes

Affected function

Behavior changed?

Notes

R4J Issue Revision

No

R4J v4.5 will display the R4J Issue Revision custom field as it was before upgrade. 

R4J Suspect

Yes

The new R4J Suspect custom field provides details on the changed issue and linked issue(s) affected. This information will show in the revision history. If unwanted, please include R4J Suspect in the field blacklist.

Word Export

Affected function

Behavior changed?

Notes

Affected function

Behavior changed?

Notes

  • Word Export Context Items

No

R4J v4.5 will render data for context items and expressions related to revisions and baselines as it was before upgrade.

REST API

Affected function

Behavior changed?

Notes

Affected function

Behavior changed?

Notes

  • 1.0

No

API responses will remain the same for REST API 1.0 endpoints. Changes in processing added for endpoints that add issues to the tree, create baselines, and delete baselines.

  • 2.0

No

API responses will remain the same for REST API 2.0 endpoints. Changes in processing added for endpoints that add issues to the tree and creating/modifying/deleting suspects.

 

Functions not mentioned are unaffected by the change in revision structure.