• Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Workflow Triggers
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      I'm a team member and admin of my team's boards, but I cannot create a post function unless I'm administrator of the ENTIRE Jira INSTANCE!  The current global admins are unwilling to allow/maintain post functions so an entire feature set of the product is going to go UNUSED.  If you didn't require FULL ADMIN capability but could enable either individual users or board admins or some level of permission less than global to add post functions in a team's workflow, that would be pretty awesome.  There are over 15,000 users in our instance and I can understand the reluctance of the small admin team to open the flood gates to everyone if they're the only one's who can do it.  Nor will they assign me global admin rights.  This is a severe limitation of a capability that should be out-of-the-box easy for anyone to use.

          Form Name

            [JSWSERVER-20929] Lessen permission requirements for Post Functions

            A possible implementation of this feature would be to build on the Automation Add-on and make it available out-of-the-box to all users, not just project admins.  Anything I can do in the UI should be something I could automate if I chose to do so.

            Chris Nagel added a comment - A possible implementation of this feature would be to build on the Automation Add-on and make it available out-of-the-box to all users, not just project admins.  Anything I can do in the UI should be something I could automate if I chose to do so.

            Chris Nagel added a comment - - edited

            I think, in fact, that any individual user should be given the ability to script anything they can do in the UI and assign it to a triggering event.   What I don't understand is the super high extra top level of access required for a simple automation task. Any user can move a story into 'Testing' and any user can assign the issue to another user, so why can I not tie the assignment to the move and set it as an automatic action? 

            Chris Nagel added a comment - - edited I think, in fact, that any individual user should be given the ability to script anything they can do in the UI and assign it to a triggering event.   What I don't understand is the super high extra top level of access required for a simple automation task. Any user can move a story into 'Testing' and any user can assign the issue to another user, so why can I not tie the assignment to the move and set it as an automatic action? 
            Chris Nagel created issue -

              Unassigned Unassigned
              2beec31a29b5 Chris Nagel
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: