Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Reindexing a smart commit doesn't update previous write actions

Tini Good
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 18, 2015

A JIRA issue number was included in the middle of a Fisheye smart commit like this:

  JIRA-123 #comment Merging JIRA-123 branch back into trunk

The JIRA comment ended up being "Merging" and it cut off everything after the JIRA key.  I edited the commit message and re-wrote it as:

  JIRA-123 #comment Merging branch back into trunk

Then I reindexed that one commit number.  I was expecting it to update Fisheye and modify the JIRA comment.  However, nothing happened to the JIRA comment. 

Is this expected behavior?

1 answer

1 accepted

0 votes
Answer accepted
lpater
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 23, 2015

Hi Tini,

I'd say it's expected. We don't reprocess smart commits when doing reindexing of any kind.

This is in order to avoid duplicating any actions that shouldn't be repeated (like transitions, comments but also creating reviews).

Tini Good
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 23, 2015

It would be awesome if: (a) smart commits could handle JIRA keys in mid-comment, possibly through an escape character (a backslash would probably work) and (b) if there was a way when reindexing in JIRA to check a box to also reprocess a smart commit. I think the first would be very universally useful, although the second is pretty specialized.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events