Not without some coding.
However, the question here though is probably more about what other button you'd want to create and why? If you're in an issue creation process, then "cancel" and "create" are pretty much the only useful options. If you could explain what you're trying to add, you might find one of us has a better approach that doesn't need hacking
Thanks Nic. Well i can explain you with the requirement. One of our partners who use JIRA extensively for issue tracking had this request. Requirement : The workflow what we designed has a flow like this . Create -> Draft -> Registered and so on So for some of them its annoying to use this type of transition as their task is not submitted directly once they have created an issue. They need to have this extra state as "Draft" . So they would want to bypass this Draft state. So one way what i thought was to have a checkbox which will check if its direct submission or a draft submission and depending on that a post function to fast track an issue. But they came up with another option of having a button. Existing "Create" button will work normally whereas another button "Direct" which will directly move the issue to Registered once it is created. So we want to maintain the same workflow with these transitions. Either Create->Submit->Registered or Create->Registered based on the need.
Thought it might be something like that. The requirement "add a button" is a huge understatement of what you want to do. It really is not that simple, as you also need to hack the entire workflow engine to enable a second create transition - Jira only has ONE create transition and that has ONE end point. Your initial solution can be done far more easily - get them to set a field for a fast-track transition listener to pick up. Another button means some serious hackery in the core of Jira.
It varies by version, and where you want the button. In the case above, the button isn't too hard - you'll need to insert it into the createissue.jsp file.
The classes behind it are slightly harder - you'll need to rewrite a chunk of the workflow engine. That's not something I'd try, it's a big project.
Metnioning @Oded Mozesh
Thanks for the fast response.
I use JIRA 7.1.4 and would like to add button to the version window (for example: http://localhost:8080/projects/PLAYT/versions/10001).
I thought I should create a plugin, but currently fails to run atlas-run even on the helloworld example )-:
Good point - if it's not required at "create time", but "when user clicks something", it's a bit easier, as you can create an add-on that exposes something in the menu your users can click and encapsulate whatever code you need to push the data to where you want it.
Or do what Chris says if it's tied to an issue.
Hi @Nic Brough [Adaptavist]
I have a similar requirement in which my client is asking for a button on the transition screens during the workflow. The reason is explained with the scenario of our project -->
One of the transition is 'Send Response' and when the user does it, a mail is sent to the addressed user from the configured mail handler. Sending mail is the most important process and when it is done, only one step remains. Since this is an important step, my client wants something like save and send, which is similar to updating the field and not actually moving through the transition. Would you let me know how adding an additional button work on the transition screen here? If it's too much work, then probably my client has to use 'Edit' on the issue screen to update the fields, but would rather be a long process as he would need to go the tab and find the required field as well. Any help would be appreciated.
Edit is the best option there - it's what it's for. You could add transitions to handle it (with a screen with only the important fields on it) but that would be overkill and look like workflow progress.
The other option is to write an add-on to provide the extra duplicated action in the menu
Thanks @Nic Brough [Adaptavist] for the quick response. Appreciate it mate.
I have said the same thing about 'Edit' button to them. Although add-on seems an option, it would end up being a redundant with Edit right being there. Will try and stick with Edit only for this requirement.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG