Uploaded image for project: 'Automation for Jira Server'
  1. Automation for Jira Server
  2. JIRAAUTOSERVER-101

Improvements to the rule import wizard

XMLWordPrintable

    • 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

            Marc Dacanay made changes -
            Labels Original: iq-a4j New: iq-a4j ril
            Marc Dacanay made changes -
            Remote Link New: This issue links to "Internal ticket (Web Link)" [ 978975 ]
            Filipi Lima made changes -
            Description Original: *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 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             		New: *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
            Filipi Lima made changes -
            Remote Link Original: This issue links to "A4J-3075 (Bulldog)" [ 712417 ] New: This issue links to "A4J-3075 (JIRA Server (Bulldog))" [ 712417 ]

            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.

            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.
            Alexander Artemenko made changes -
            Description Original: *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 overwrite rules (if the rule id, name and context matches)
            - Option to import rule owners (will need to add it to the export)
            - Ability to map custom fields and custom fields options that have different IDs on source and destination instances             		New: *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 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
            Michelle Chin made changes -
            UIS New: 0
            Rudy Slaiby made changes -
            Labels New: iq-a4j
            Daniel Ramotowski made changes -
            Remote Link New: This issue links to "Page (Atlassian Documentation)" [ 712572 ]

            Daniel Ramotowski added a comment -

            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.

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

                Created:
                Updated: