• 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.

      Originally reported via the AUI project in AUI-4211, but it's a feature request for Jira Software.

      —

      An updated timestamp make it look as if I've been working on the issue, but I haven't.

      Similarly, I might not want to send email notifications just because I drag around a couple of co-worker's issues on a shared Agile Board.

      If I move an Issue vertically in an Agile board, the only thing changed is the rank.
      To me, this is a "non-action", since no actual work has been done on the Issue itself.
      So I don't want the Updated timestamp to be changed.
      I also want to be able to prevent email notifications to be sent for this minor change to the issue.

      When people list issues, they usually sort the results by last Updated and expect to see the issues currently being worked on at the top. Therefore, these non-changes should not update the Updated timestamp.

      That's why I'm requesting two configuration options in the Agile Board settings.

      (
      Note that the above only applies to rank changes using drag n drop in the agile board.
      It does not apply to the situation where I open an Issue and choose "Rank to top" or "Rank to bottom".
      )

      Please add two options to a board's general configuration to control:

      ...
      ...
      Filter Query: blah blah blah
      Ranking: Using rank
      [x] Don't change the issue's updated time when changing rank
      [x] Don't send notification email when changing rank
      Projects in board: blah blah blah
      ...
      ...
      

            [JSWSERVER-16317] Don't touch an issue's updated time when only its rank is changed

            Maybe this helps someone: Rather than filtering by "Updated time", it is possible (and maybe that what you actually want) to filter explicitly by the time of a status change. JQL supports this for example:

            status != Closed OR status CHANGED TO Closed AFTER -1w
            

            I used this as a board sub-filter instead of the default - so any old modified issues won't be shown again in the "Done" column.

            Mark Plomer added a comment - Maybe this helps someone: Rather than filtering by "Updated time", it is possible (and maybe that what you actually want) to filter explicitly by the time of a status change. JQL supports this for example: status != Closed OR status CHANGED TO Closed AFTER -1w I used this as a board sub-filter instead of the default - so any old modified issues won't be shown again in the "Done" column.

            Agree. Closed issues appear in the Kanban board Closed-Column again when just changing the rank. (One workaround is, to use a Board-Sub-Filter with a Filter by "Resolved" date ... but it has other disadvantages)

            Mark Plomer added a comment - Agree. Closed issues appear in the Kanban board Closed-Column again when just changing the rank. (One workaround is, to use a Board-Sub-Filter with a Filter by "Resolved" date ... but it has other disadvantages)
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3070527 ] New: JAC Suggestion Workflow 3 [ 3653660 ]

            Agree. The ranking impact on dates makes time filters very hard to use.

            Ranking might be stored as information separate from the issues and manage its own notifications/times.

            Laurent Di Cesare added a comment - Agree. The ranking impact on dates makes time filters very hard to use. Ranking might be stored as information separate from the issues and manage its own notifications/times.
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2627255 ] New: JAC Suggestion Workflow [ 3070527 ]
            Kasia Derenda made changes -
            Remote Link Original: This issue links to "Page (Extranet)" [ 346462 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2497298 ] New: Confluence Workflow - Public Facing v4 [ 2627255 ]
            Status Original: Open [ 1 ] New: Gathering Interest [ 11772 ]
            Kasia Derenda made changes -
            Remote Link New: This issue links to "Page (Extranet)" [ 346462 ]

            Daz added a comment -

            In relation to the configuration for email notifications, JSWSERVER-9706 was raised some time ago and touches on this theme, so I've linked the issues together.

            Daz added a comment - In relation to the configuration for email notifications, JSWSERVER-9706 was raised some time ago and touches on this theme, so I've linked the issues together.
            Daz made changes -
            Link New: This issue is related to JSWSERVER-9706 [ JSWSERVER-9706 ]

              Unassigned Unassigned
              dbf4e39b87a3 Elof Ofel
              Votes:
              10 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: