Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-20439

Reference to automation rule in issue history

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Issue - Fields
    • None
    • 1
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NB: This feature suggestion is for "Automation for Jira", but I haven't been able to create the ticket there. The reason is when creating an issue, the "Component/s" field is mandatory but there is no "Component/s" values available in "Automation for Jira" project.

      For the moment, the entry in issue history for Automation changes has nothing specific, there is no difference between an automatic and a manual change. It's as if the "Actor" of the rule has made manual changes to the issue (leading to questions by suspicious colleagues like "Why did you make such and such changes to this ticket? - I never even seen your tickets... Oh wait.").

      It would be great to have a reference to the Automation rule in issue "History" tab (or somewhere else), so that:

      • users know that the changes were made by an automated rule
      • we can easily track down a rule causing undesired side effects

            [JSWSERVER-20439] Reference to automation rule in issue history

            No work has yet been logged on this issue.

              Unassigned Unassigned
              dfcda3426402 adesir
              Votes:
              3 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: