I want to add a button that generates a new issue from the issue view?

[Scott Federman]

Hey all, 

I have a customer who needs to have things very much in their face to be able to use Jira. One of those things they deal with are approvals. These approvals are created using approval type sub-tasks. Right now, i have a selection under the automation menu that will generate these sub tasks based on a manual trigger.  The concept seems to work but they never remember to look under the automation lightning bolt to find the create approval button. Has anybody added a button to the view screen? Can somebody help me out with a way to add a button to the view screen that would kick off this automation?

[John Funk]

Hi Scott,

What if you created a custom field with just a checkbox or a Yes/No radio button or such. Then change your automation rule to fire with the field value is changed. Then add the field to the screen of course and suggest each person pin the field to the top of the screen for visibility. 

Then you can even add a Validator to the transition to make sure the field is changed before they can move on. 

[Scott Federman]

the problem here is that i potentially need to have multiple approvals created. It may be one approval required. It may be 10. A check box would only allow for one at a time. With the dropdown they can currently select the option as many times as needed and prompt the fields needed. 

[John Funk]

Are sub-tasks created on every approval? 

[Scott Federman]

the sub task is the approval.

[John Funk]

I am totally lost then. What is the exact use case/scenario? 

[Scott Federman]

no worries. the use case is i have a story level ticket. the ticket may require multiple approvals from multiple different people. Those approvals are captured using a subtask issue type. So one subtask per approver. Instead of going to the "More" dropdown option in the issue view and selecting "create a sub-task" i want to add a button somehow on the issue view screen that will essentially provide the same functionality. 

[John Funk]

Why are you creating sub-tasks to get the approvals? Why not just put the approval required on the transition? 

[Scott Federman]

because there are multiple people who will be required to approve. the approvers will be different and the amount of approvals will be different depending on the work. Even the times when an approval is required may change. Putting them in the workflow as a transition will limit the amount of approvals i can do to one time without a mechanism to require additional approvals at alternative times. We also need to monitor the approvals so the approvers know what to approve and when on a dashboard as well as require all approvals to be complete to transition the task to close. This is not a typical client unfortunately with what would typically be a simple request. Its a simple request with a rather complex solution for a very non-technical client. The button allows me to solve for multiple issues and scenarios.

[John Funk]

I still think you can accomplish this with the workflow. There is no problem having multiple approval steps in the workflow. And you can control what users are put in the Approvers field based on Conditions in an automation rule. Much cleaner this way with a lot less work items getting created and having to be managed. 

[arielei]

Hello @Scott Federman 

There arent any good apps that can add buttons.

What about using the workflow transitions? for example, create the workflow in the manner that would suite their needs, and once they need it, they will press the transition and it will kick start the automation.

let me know what you think.

Ariel.

[Scott Federman]

formally that would have been the easy way. But now that atlassian got rid of the buttons and put them as a dropdown, its the same issue as the automation button. I know it can be done using forge. I unfortunately don't know how to use forge or develop for that matter lol.