nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How can we help your organisation spend less time on Jira doing repetitive busywork?

Joe Nguyen_lvma1a

I'm a PM for Jira, and we're looking to invest in improving Automations in Jira.

Do you have any ideas or suggestions? (AI ideas welcome too!)

👉 Share your thoughts in our super-quick open survey: https://forms.gle/QnkSr16QGVDLibBx7

Or book in a call to chat further: https://calendar.app.google/WQjRJFd4YSf9aFTk9

Your insights will directly influence our roadmap as we look to expand automation capabilities, improve discoverability, and enable more AI-powered workflows in Jira so you spent less time clicking the same things over and over, and more time doing the work that excites you - that which takes creativity and ingenuity.

Comments

Stefano Vidonis_1ub6cl

I have received 3-4 email for this argument, stop spamming around please

Krzysztof Bogdan_oue0pi

Hello @Joe Nguyen

As an app developer - I would love to see possibility to extend
Jira Automation with app specific actions.

Krzysztof Bogdan_oue0pi

Yea me too. Something is off

Cash Coyne_tanpr0

Hi @Joe Nguyen , our security software is blocking the forms.gle site. So here is my list:

For Automations:

Under Rule Details, be able to limit the rule only on selected issue types.
Have nested if else statements
Allow branching in if else statements
For On Demand Automations:
- Allow a user to enter data into fields that can be used in the automation
- Allow a popup confirming or giving error like you do when you clone an issue
- Be able to have restrictions on what can trigger it, not just Groups that can trigger. Ie:
  - Limit it to certain issue types
Be able to select multiple components at once for duplicating and moving
Be able to copy a component or multiple components from one rule to another
Be able to copy an if/else component as a different if/else component and it NOT be an else if component
Be able to move an if/else component off the branch
Be able to move a Related Issues branch to an if-else branch (you can't move one there, but you can create one there)
Be able to add an if statement to an if-else branch
Be able to select multiple boards when using Sprint Started trigger
Be able to have comments on components or just inline
For the global Audit Log, be able to filter entries by scope and owner
Have a Search and replace that will find and replace text in components
Have a search for specific text in fully expanded Audit log on a page, and in a date range

Stefano Vidonis_1ub6cl

Crazy!

Gary Spross

The form is a bit to rigid to indicate the improvements I would like to see made. Here are a couple improvements I would like to see within automations:

Ability to sort automation rules list on each column
Ability to filter automations by project association
Ability to scope to
- Project categories
- Specify issue (work item) types
Additional levels of nesting
Ability to drag and drop all types of components (i.e. branches)
Ability to copy if/else components to a different branch (not as else)
Ability to reorder else conditions
Ability to move else conditions outside of specific if/else branch
Clearer indication of fields in select lists
- When field names are duplicated, you can't tell in the list which is which
Formatting assistance (an "intellisense" type of feature)
- For actions to populate text fields
  - i.e. Paragraph fields, Comments, Slack messages, etc.
- For the "Additional fields" section of the "Edit Issue" component
Better search capabilities within the audit log
- Ability to filter by status
Ability to sort on each column within audit log
Ability to add notes/comments to components to explain more complex logic
- Especially helpful when complex JQL is being used
Ability to increase the size of text fields for better visibility as it is filled out or to see all of what is contained within it
- i.e. Log action text block

These are some things I could think of off the top of my head.

Gary Spross

An additional 2 improvements that would be massively helpful...

When a project or field is deleted, have a way to filter impacted automations
- A notification to the Jira admins would be nice as well
When a field name is changed, some components auto updated, but others do not
- Field name changes should update automatically in all aspects of the automations rules

Tere Pile

Increase allowance would be nice!

Rune Rasmussen

For the point of:

For On Demand Automations:
- Allow a user to enter data into fields that can be used in the automation

This is available already with the "Manual Trigger" where you can make it pop up and require input to fields specific to only this automation, and these can then be referenced with Smart Values in the automation rule.

Cash Coyne_tanpr0

Yeah @Rune Rasmussen , I don't know why I included that as I'm already using it!

Gary Spross

Another one: Addition of a component to determine if the in scope issue is deleted or archived (inaccessible) to avoid nuisance errors.

I got a feature request created for this one, so if you agree, vote for it!

https://jira.atlassian.com/browse/AUTO-1903

Troy Anderson_htyevj

Questions/forums should separate app developers from actual Jira users. Two completely different conversations.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-administration

automation

jira-automation