Uploaded image for project: 'Advanced Roadmaps'
  1. Advanced Roadmaps
  2. JPOSERVER-2060

Parent Link and Team fields are being audited in History even when they're not updated

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • 3.29.6, 8.15.1
    • 3.29.0, 3.29.1, 3.29.2, 3.29.4
    • Historical

      Summary

      When there is no change to the Parent link or Team field (new value is same as old value), the issue history is still tracking this information like a value change with every single change to any other issue field.

      Steps to Reproduce

      1. Open an issue in Jira with Parent link and Team fields showing up on issue view and edit screens
      2. Set the Parent link value to point to another issue
      3. Notice the issue history tracks this change
      4. Set the Team value
      5. Notice the issue history tracks this change
      6. Edit the issue and change another field such as priority, description, ...

      Expected Results

      Issue history should only track the new change made

      Actual Results

      Issue history logs the change to the field along with Team and Parent link and display unchanged values.

      Notes

      Along with recording a change for Parent Link, "issuelink_deleted" and "issuelink_created" events are fired because the issue link for the parent issue is indeed removed and recreated. This may needlessly cause automations to fire.

      LOG:  execute <unnamed>: DELETE FROM public.issuelink WHERE ID=$1
DETAIL:  parameters: $1 = '10705'
...
LOG:  execute <unnamed>: INSERT INTO public.issuelink (ID, LINKTYPE, SOURCE, DESTINATION, SEQUENCE) VALUES ($1, $2, $3, $4, $5)
DETAIL:  parameters: $1 = '10706', $2 = '10300', $3 = '10501', $4 = '10800', $5 = NULL

        1. image-2017-11-28-16-24-27-445.png
          image-2017-11-28-16-24-27-445.png
          2 kB

          Form Name

            [JPOSERVER-2060] Parent Link and Team fields are being audited in History even when they're not updated

            Pierre EK added a comment -

            Not to mention the audited value is meaningless? What do these IDs refer to? Moreover, if we empty the Parent Link field, this change is not audited either  and it messes us the search too, because a JQL as "Parent Link" is EMPTY would no longer return the issue, even after performing a Re-Index  

            We are honestly regretting buying this product...  thought that it would be better than others as it is provided by Atlassian, but clearly it's not the case, as providing a simple Custom Field was so messed up that it was not even searchable, nor can be used in dashboards for statistics, not even audited, and filling its value or clearing it does not work properly, among other issues...

            Pierre EK added a comment - Not to mention the audited value is meaningless? What do these IDs refer to? Moreover, if we empty the Parent Link field, this change is not audited either  and it messes us the search too, because a JQL as "Parent Link" is EMPTY would no longer return the issue, even after performing a Re-Index   We are honestly regretting buying this product...  thought that it would be better than others as it is provided by Atlassian, but clearly it's not the case, as providing a simple Custom Field was so messed up that it was not even searchable, nor can be used in dashboards for statistics, not even audited, and filling its value or clearing it does not work properly, among other issues...

              7a9938a523de Anne Jang
              ed44d60068b3 Gowri Kumar
              Archiver:
              atibrewal@atlassian.com Aakrity Tibrewal

                Created:
                Updated:
                Resolved:
                Archived: