Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-79704

Ability to set Custom Confluence Automation Rules to Smart Buttons

    • 11
    • 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.

      Problem Definition

      Confluence Automation currently offers the possibility for users to add rules from pre-defined templates to a Smart Button on a page.

      Even if an admin builds a new automation rule, the users currently can't assign those to Smart Buttons.

      Suggested Solution

      Implement the ability to assign custom pre-made automations to the Smart Buttons.

            [CONFCLOUD-79704] Ability to set Custom Confluence Automation Rules to Smart Buttons

            I'm a little surprised that this needs to be a feature request, and not considered MVP - All of the automations that are pre-defined button actions are esoteric, limited and fairly useless without some customisation. Do you have usage stats on them? I imagine they are very low.

            Even Atlassian support thought that the rules that the buttons create were editable.

            Please fix this. 

            Dan Horsfall added a comment - I'm a little surprised that this needs to be a feature request, and not considered MVP - All of the automations that are pre-defined button actions are esoteric, limited and fairly useless without some customisation. Do you have usage stats on them? I imagine they are very low. Even Atlassian support thought that the rules that the buttons create were editable. Please fix this. 

            This feature would unlock so much potential for our templates, and allow us to make sure certain steps are always performed when releasing new software to clients. Right now, the testers and product owners have to click the page and select the right automation whenever they need to do the things we have automated for them, which is easy to forget and feels like a hassle. So, every werek someone forgets something. A big, visual button is hard to miss, though. Please consider raising the priority of this suggestion! πŸ™

            Marit Kristine Berntsen added a comment - This feature would unlock so much potential for our templates, and allow us to make sure certain steps are always performed when releasing new software to clients. Right now, the testers and product owners have to click the page and select the right automation whenever they need to do the things we have automated for them, which is easy to forget and feels like a hassle. So, every werek someone forgets something. A big, visual button is hard to miss, though. Please consider raising the priority of this suggestion! πŸ™

            I have created some custom automation rules in Confluence and then realised that I cant link them to a smart button. This would be really useful for me and my colleagues

            Paul Sallis added a comment - I have created some custom automation rules in Confluence and then realised that I cant link them to a smart button. This would be really useful for me and my colleagues

            The smart button functionality is very limited and greatly reduced in value compared to being able to trigger custom automations. The feature feels under-cooked. I can only hope the current implementation wasn't considered the end game for the smart button

            Dave Furlani added a comment - The smart button functionality is very limited and greatly reduced in value compared to being able to trigger custom automations. The feature feels under-cooked. I can only hope the current implementation wasn't considered the end game for the smart button

            Guillaume Beaulieu added a comment - - edited

            That would help immensely our team we could use that to create Jira templates that would be filled through automation so that we gather the right information on any type of requests without creating multiple issue types. Since the feature by itself is already present, it doesn't seem like a lot of effort for the usage that it would gather.

            Guillaume Beaulieu added a comment - - edited That would help immensely our team we could use that to create Jira templates that would be filled through automation so that we gather the right information on any type of requests without creating multiple issue types. Since the feature by itself is already present, it doesn't seem like a lot of effort for the usage that it would gather.

              Unassigned Unassigned
              fb5c5276e5ff Caio Oliveira
              Votes:
              24 Vote for this issue
              Watchers:
              22 Start watching this issue

                Created:
                Updated: