Not override the functionality of the JIRA Create button
I think the decision to override JIRA's big, blue Create button in the top navigation is a mistake. And it's causing some headaches on our end. We have non-technical users who are using the Structure (with edit permissions) who aren't aware that creating a new issue will add it to the Structure they're viewing. They simply want to create an issue, not necessarily add it to their structure. We could remove the button easily, but then we'd have to have our users jump to another JIRA screen to create an issue. That's design breakage! My opinion is, leave the ubiquitous Create button alone. Users can use the grid to add issues to the structure. The Create button would be JIRA proper, not Structure overridden. If you must insist on modifying the Create issue button and dialog, why not make "add to structure" an OPTION, NOT the DEFAULT?
Reviewing options – please see comments
-
Peter commented
Hi Igor,
It was a long time ago this was written. But... I actually share this exact same frustration as Hugh.
Why is it default to "add to structure". It should be the other way around. Many people forget to click "don't add to structure" and it will mess things up.
If you or any other of your colleagues are seeing this, please revert as we need a workaround asap.
-
Hugh, no problem, thanks for speaking your mind! We value feedback very much.
There's no current plan to address it, since we have started talking about it 5 minutes ago, but we'll review this on our next UI planning session.
As for workarounds, there are no setting in Structure, but a JIRA admin armed with JavaScript could do that by clearing "window.almworks.structure.installCreateIssueHandler" property after scripts have loaded, but before this function is executed.
For example, you can set up an "Announcement Banner" in JIRA (in System settings) like this:
<script>try { window.almworks.structure.installCreateIssueHandler=null; } catch (e) {}</script>
However, that would add an unneeded banner stripe on every page (unless you have other banner there).
Other ways to inject that code in the right place could be used.
Hope this helps!
Igor -
Hugh Hiers commented
Sorry about the gripe. I know there's always a weighing of the options for specific use cases. But in our neck of the woods, our use case is the one I described. The only options I have now are to remove edit permissions for the users or remove the button. Neither of this is desirable. Is there some other hack you know of that's not too painful? Is there a plan to make overriding the button an option?
-
Hugh, thanks for your comment!
I'm sorry if overriding Create button's behavior is an inconvenience. I myself often click "Do not add to Structure" at the bottom of the dialog after I have clicked "Create".
However, this functionality, as far as I remember, was added specifically to address other customers' requests. And it was also justified by non-technical users having difficulties in adding issues to a structure, since they were accustomed to clicking the blue Create button.
We'll obviously need to find some middle ground here.
Kind regards,
Igor