-
Suggestion
-
Resolution: Unresolved
-
None
-
0
-
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
- was cloned as
-
- Closed
- links to
- mentioned in
![[Atlassian Documentation] Page](https://confluence.atlassian.com/images/icons/favicon.png "[Atlassian Documentation] Page"){kind=icon}
- relates to
-
![[JIRA Server (Bulldog)] Story - Created by Jira Software - do not edit or delete. Issue type for a user story.](https://bulldog.internal.atlassian.com/images/icons/issuetypes/story.svg "[JIRA Server (Bulldog)] Story - Created by Jira Software - do not edit or delete. Issue type for a user story.")
A4J-3075
You do not have permission to view this issue
[JIRAAUTOSERVER-101] Improvements to the rule import wizard
| Labels | Original: iq-a4j | New: iq-a4j ril |
| Remote Link | New: This issue links to "Internal ticket (Web Link)" [ 978975 ] |
| 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 |
| Remote Link | Original: This issue links to "A4J-3075 (Bulldog)" [ 712417 ] | New: This issue links to "A4J-3075 (JIRA Server (Bulldog))" [ 712417 ] |
| 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 |
| UIS | New: 0 |
| Labels | New: iq-a4j |
| Remote Link | New: This issue links to "Page (Atlassian Documentation)" [ 712572 ] |
| Remote Link | New: This issue links to "A4J-3075 (Bulldog)" [ 712417 ] |
| 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) |
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) - Ability to map custom fields and custom fields options that have different IDs on source and destination instances |