• 0
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Issue Description

      Currently, the Automation rule import wizard contains very limited options, which can make it very tedious/unpractical to import a JSON file containing a big number of rules.

      Suggestions

      Some improvements to the wizard that help sys-admins save time especially on large instances:

      • An option to select all rules when importing
      • An option to select all active rules when importing
      • UI should differentiate rules that have the same name (maybe show the project context / rule ID)
      • An option to import rules in its exported state (vs DISABLED by default)
      • Option to import rule labels and create them if missing
      • Option to overwrite rules (if the rule id, name and context matches)
      • Option to import rule owners (will need to add it to the export)
        • Import should honor “actorAccountId”/“authorAccountId” values defined in source JSON and map them accordingly after importing the rule (given that provided usernames exist in the target system)
      • Ability to map custom fields and custom fields options that have different IDs on source and destination instances

            [JIRAAUTOSERVER-101] Improvements to the rule import wizard

            I have a couple of additional suggestions.

            • Ability to map issueTypes, statuses, transitions, projectIds options that have different IDs on source and destination instances.
            • Ability to Map Project Level Assignee, Group Head options that have different IDs on source and destination instances.

            Dhananjay Yadav added a comment - I have a couple of additional suggestions. Ability to map issueTypes, statuses, transitions, projectIds options that have different IDs on source and destination instances. Ability to Map Project Level Assignee, Group Head options that have different IDs on source and destination instances.

            A4J 8.1 1 will provide ability to select all rules in the import screen.

            Daniel Ramotowski added a comment - A4J 8.1 1 will provide ability to select all rules in the import screen.

            I have a couple of additional suggestions, which Atlassian Support said I should comment with on this ticket for their inclusion:

            1. Each time you import a rule, the Owner and Actor fields get set to the person running the import. I would like those to always stay the same as what they were when the rule was first written. I currently have to go in and update one or both after an import
            2. It would be nice if the export/import process kept labels intact. I currently need to reassign labels to the rules each time they're imported, and if I deleted the old versions first, the labels disappear altogether

            Dov Frankel added a comment - I have a couple of additional suggestions, which Atlassian Support said I should comment with on this ticket for their inclusion: Each time you import a rule, the Owner and Actor fields get set to the person running the import. I would like those to always stay the same as what they were when the rule was first written. I currently have to go in and update one or both after an import It would be nice if the export/import process kept labels intact. I currently need to reassign labels to the rules each time they're imported, and if I deleted the old versions first, the labels disappear altogether

              Unassigned Unassigned
              jrey Julien Rey
              Votes:
              39 Vote for this issue
              Watchers:
              31 Start watching this issue

                Created:
                Updated: