Loading...

XML

Word

Printable

Type: Suggestion
Resolution: Unresolved
Component/s: None
Labels:
- jsw-s13

Feedback Policy:

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.

Suggested improvements

When creating an automation rule using an action to set a field, if a custom field is used any update to the field name (rename) will cause the field to be recognized as a deleted field in the automation rule. For example, if a field is named "Example id" and you change it to "Example ID" it will be recognized as a deleted field due to the capitalization if "id". In the field mapping for the automation rule use the field ID as the mapping variable instead of the field name when using the "Choose which filed to select..." option, so that when a filed name is altered the rule will still map to the renamed field
When we create a new sub-task via automation, we should be able to set a parent id besides "current issue" or "trigger issue"
Make it easier to work with fields, e.g. Improve Automation Rules so they accept keys and names for the Project and Issue Type fields instead of just the Ids
Issue field compare condition should use the ID of Request Types
Renaming an Issue Security Level does not update linked automations, causing failures

.Screen Shot 2022-04-29 at 2.47.32 PM.png

- - Sort By Name
  - Sort By Date
  - Ascending
  - Descending
  - Thumbnails
  - List

Screen Shot 2022-04-29 at 2.47.32 PM.png
154 kB
29/Apr/2022 9:50 PM

duplicates

AUTO-161 Automation fails when it has two fields with the same name/type, showing the error "Found multiple fields with the same name and type:" and Additional fields contains invalid field(s) in 'update' or 'fields' section. <field_name>"

Long Term Backlog

is blocked by

AUTO-310 Update request type names on Automation rules when modified in Jira

Closed

AUTO-420 Allow custom fields with same name in Automation using custom field ID

Closed

AUTO-883 Renaming an Issue Security Level does not update linked automations, causing failures

Closed

is duplicated by

AUTO-1551 Issue Action UI - Issue field duplicated with any change if there are 2 custom fields with same label selected

Closed

AUTO-180 Automation component actions are not updated when Jira component names are changed, e.g. Epic Link field fails if Epic issue types have been renamed

Closed

AUTO-1294 Default and custom context field options appear as duplicates and when a custom context is deleted the selected options continue to appear in the ticket UI

Closed

AUTO-307 Issue field compare condition should use the ID of Request Types

Closed

AUTO-386 When we create a new sub-task via automation, we should be able to set a parent id besides "current issue" or "trigger issue"

Closed

AUTO-523 Make it easier to work with fields, e.g. Improve Automation Rules so they accept keys and names for the Project and Issue Type fields instead of just the Ids

Closed

AUTO-1404 Automation Condition Issue Fields: Update Automation Conditions for their values when said values are updated elsewhere.

Closed

is related to

JRACLOUD-76466 Jira should store the custom field details based on field ID instead of the field name

Closed

JRACLOUD-61048 As a jira admin asked to rename a custom field, I want to know which filters contain the custom field, so I know which ones to update

Gathering Interest

(6 is duplicated by, 2 is related to)

Assignee:: Unassigned

Reporter:: Earl McCutcheon

Votes:: 55 Vote for this issue

Watchers:: 27 Start watching this issue

Created:: 29/Apr/2022 9:50 PM

Updated:: 06/Dec/2024 5:27 PM

Details

Description

Suggested improvements

Attachments

Attachments

Issue Links

Forms

Activity

People

Dates