Automation UI Feature Request - Labels interface is error-prone

Casey Gould May 23, 2023

After encountering this issue several times, both in automations I've created (even after knowing better!) and automations created by others, I believe that the current UI to edit labels via Jira automation isn't clear enough about the action being taken.

The default to Set (override and replace) here in automations is also inconsistent with the default to "Add to existing" in the Bulk edit flow.

This leads to repeated errors of overriding all existing labels when the user intended (and probably expected) to simply add the selected label(s) to the existing ones.

Steps to reproduce

  1. Create an Automation (Jira Cloud)
  2. Add an "Edit issue fields" component
  3. Select "Labels" as the field to edit

Current Behavior

Screenshots are included below.

  • See a box with prompt "Type to find value..."
  • See a toggle that says "More options" that then shows you advanced, JSON-based editing
  • If you type into the box, you can select or create a label. You then see that label in the box.
  • Nowhere does the UI warn you that you have just told the automation to overwrite all existing labels and replace them with the one(s) selected here.
  • The word 'set' is used as in "Choose fields to set.." but looks like an unrelated action (choosing fields) and doesn't make it clear you're setting all the labels on the issue to just these.
  • IF you think to click the ... to the right of the label selection box, you see three options: SET, ADDREMOVE, and COPY.
  • If they see this dropdown, I believe this is usually where people realize that they need to specify ADDREMOVE instead, but most of the time they don't even get there.
  • If you do select ADDREMOVE, the text defining the boxes as add vs remove are no longer visible as soon as you add a label.

Proposed Behavior

The Automation Edit UI for labels should be more like that on the Bulk Edit flow, which defaults to "add to existing" and makes it clear that there are multiple options for altering the labels.

1. Default the edits to "Add to existing"

This is considerably easier to undo if the user meant to do something else than the current behavior to remove all existing labels.

2. Clearly state the edit action type (SET, ADD, REMOVE, COPY) selected and have this action type continue to be visible even when labels have been added

3. Clearly show that there are multiple action types to use, whether through a dropdown indicator like the Bulk edit flow, showing all four types, or something else.

 

Screenshots

Illustrating points from above:

Image 1) Default view for editing labels isn't clear this is set and override.

Edit_Issues_Landing.png

Image 2) More options is about advanced editing, not more ways to set labels. This makes sense in the general edit fields use case but makes the ... even less intuitive.

Edit_Issues_MoreOptions.png

Image 3) Selecting ... shows more options for editing labels.

Edit_Issues_SelectType.png

Image 4) Selecting a label removes visibility to the edit type (here the prompt text was "Values to add" before a label was selected. No context on the edit type at all if labels are selected in both sections.EditIssues_AddRemove_LabelSelected.png

Image 5) This is the default for "Change Labels" under Edit Issues in the Bulk Edit flow. The default is "Add to existing" and the dropdown style makes it clear there are other options available.

BulkEdit_ChangeLabels.png

 

Please consider these UI updates, they would make it easier to visually check that the automation is set to do what you intended and save quite a bit of pain trying to undo where automations have (unintentionally) overridden existing labels.

To my colleagues whose labels I accidentally removed this week - my apologies! 

0 comments

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events