Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-15181

Make bulk move operation more user-friendly during field update stage

    XMLWordPrintable

Details

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

    Description

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      As an example the reporter field may require a value during the bulk issue operation. The reason why the reporter field needs a value is that this field is required. When you check the retain option, the reporters are retained where possible. Depending on your configuration this may not be the case for all issues being moved. For those issue a new (reporter) value needs to be set and that's why the reporter field needs a value set.

      JIRA could be a bit smarter & user-friendlier and not require a value in the case when all issues will be able to retain the original reporter. It could also inform the user that if the value is entered and retain option is checked, it will only replace or set the reporter value for the issues that will require it. It would seem that at the moment the current message does not give enough confidence to the users, they fear that all values will be replaced.

      Please see linked JRA-14385 for more details about the origin of this issue.

      Attachments

        Issue Links

          is cloned from

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-14385 Bulk move where reported should be retained gives "reporter is required" error

          • Medium - Medium priority issues
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-15769 During bulk move, retain checkbox doesn't work for reporter

          • High - High priority issues
          • Closed

          Suggestion - JRASERVER-27198 Move Issue Configuration

          • Closed

          Suggestion - JRASERVER-16476 Do not force changing the assignee or reporter when keeping the issue in the same project during the move or bulk move operation or issue type migration

          • Gathering Interest
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-12165 Unclear error message when bulk moving issues whose reporter cannot create issues

          • High - High priority issues
          • Closed

          Suggestion - JRACLOUD-15181 Make bulk move operation more user-friendly during field update stage

          • Closed
          mentioned in

          Wiki Page Loading...

          Activity

            People

              Unassigned Unassigned
              dushan@atlassian.com Dushan Hanuska [Atlassian]
              Votes:
              31 Vote for this issue
              Watchers:
              15 Start watching this issue

              Dates

                Created:
                Updated: