Table of Contents | ||||
---|---|---|---|---|
|
Info |
---|
R4J 4.5 has not been officially released. Want to test out R4J 4.5 BETA? Reach out to us through our service desk portal to get access. |
Project Activation
Affected function | Behavior changed? | Notes |
---|---|---|
| Yes | Project activation will be immediate since revision history generation is removed. |
| No | R4J v4.5 project deactivation will be as it was before upgrade. Deactivating a project does not delete revision history data. |
...
Affected function | Behavior changed? | Notes |
---|---|---|
| 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. |
| 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. |
| 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. |
...
Affected function | Behavior changed? | Notes |
---|---|---|
| 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. |
| 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. |
| 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. |
...