Details
-
Bug
-
Resolution: Invalid
-
Low
-
None
-
2.6.0
-
None
Description
This appears related to CRUC-5162.
The rescan feature in FishEye/Crucible is not updating the comments in Fisheye and not updating the link in JIRA.
After changing the JIRA Issue key in a submitted Perforce changelist (e.g. TS-100 ... changed to TS-101...), and executing a rescan on that changelist the following events are expected:
1) The comment in Fisheye reflects the updated description
2) The 'links' in JIRA are updated to reflect the change (i.e. issue TS-100 no longer references the changelist, and TS-101 references the changelist)
3) The changelist comment in JIRA is updated to reflect the change
Items 1 & 2 are not occurring without a full re-index of the repository.
Steps to Reproduce
(Assumes JIRA/FishEye integration is configured and functioning properly)
1) Create JIRA issues TS-100 & TS-101
2) Submit Perforce changelist with description 'TS-100 - Rename/move files(s)'
3) Confirm FishEye and issue TS-100 reflect submitted changelist
4) Edit description in Perforce changelist created in step 2 to 'TS-101 - Rename/move files(s)'
5) Perform Rescan in FishEye UI specifying Perforce changelist created in Step 2 in From and To revision.
Expected Results:
1) The 'Source' tab in JIRA for issue TS-100 is empty (i.e. no longer references the changelist)
2) The 'Source' tab in JIRA for issue TS-101 shows the perforce changelist information
3) The FishEye dashboard for the user that submitted the changelist is updated to reflect the updated changelist description.
Actual Results:
1) The 'Source' tab in JIRA for issue TS-100 still shows the perforce changelist information (although the description reflects the change)
2) The 'Source' tab in JIRA for issue TS-101 is empty
3) The FishEye dashboard for the user that submitted the changelist shows the old changelist description
Thanks,
Craig