Loading...

XML

Word

Printable

JIRA Software Server 7.6.1
FishEye 4.5.2
Subversion repository (Tortoise SVN used in these examples)

Scenario 1: I accidentally included the wrong issue key in my commit message

Have a JIRA project with two issues: MYPROJECT-1 and MYPROJECT-2. Neither of these issues has any commits associated with them.
Make a SVN commit with MYPROJECT-1 in the commit message, and wait for the commit to display in JIRA on the issue dev panel as expected.
Change the commit message in SVN. Remove MYPROJECT-1 and insert MYPROJECT-2.
Reindex the revision properties of that rev in FishEye.

EXPECTED:

ACTUAL:

The dev panel still appears on MYPROJECT-1 and shows "1 commit." Clicking this link throws an error:
"You don't have access to view all related commits. Please contact your administrator."
MYPROJECT-2 displays 1 commit and it is this commit. As expected, clicking on the link brings up the commit and it can be viewed.

Scenario 2: "Oops! I did it again." Now the commit count is wrong.

Make a new SVN commit with a message linking to MYPROJECT-1.
Observe and note: MYPROJECT-1's dev panel no longer displays the error message described above, and it now displays the commit that was just sent.
Change the commit message in SVN to point to MYPROJECT-2.
Reindex the revprops of that revision in FishEye.

EXPECTED:

MYPROJECT-1 no longer has a dev panel because it has no commits
MYPROJECT-2 displays two commits, and the dev panel says "2 commits" at the head

ACTUAL:

MYPROJECT-1 has a link in the dev panel which reads "1 commit" and an error is displayed when clicking on it:
"You don't have access to view all related commits. Please contact your administrator."
MYPROJECT-2 displays two commits as expected, but the dev panel header reads "1 commit"

The fix described in FE-6953 works to address these scenarios as well. Specifically, you can manually delete cached data from the JIRA database.

For example, if you discover that issue ABC-123 is affected (it has 1 commit but DevPanel doesn't show), you may:

Run this REST call to confirm it has 1 commit:

<FeCru_BaseURL>/rest/remote-link-aggregation/latest/aggregation?globalId=ABC-123

Run this SQL query in Jira db to confirm Jira has an outdated record of it (no commit):
```
select * from entity_property where json_value like '%ABC-123%';
```

For JIRA 7.9+, run this query instead:
{code:java}
select * from AO_575BF5_DEV_SUMMARY where json like '%"ABC-123"%';

If the above are confirmed, it's safe to delete the db entry for it to be rewritten with up-to-date data:

delete from entity_property where id = <ID from the above SELECT query>;

For JIRA 7.9+, run this query instead:

delete from AO_575BF5_DEV_SUMMARY where id = <ID from the above SELECT query>;

These issues do not appear to occur in JIRA 7.8.1.
~~FE-6953~~ was reported as fixed in FishEye 4.5.1, but the issue described here is occurring with FishEye 4.5.2.