Can you customize the "assign" and "closed" buttons / screens?

[Brian Sweet]

There are "closed" and "assign" buttons by default, but they cannot be customized, so I created my own "assign members" and "closed" buttons + screens.

Can the default "closed" and "assign" buttons / screens be modified at all? If not, can they be removed altogether? It's confusing to users as there are basically two of each button.

[Randy]

No, you can't customize those screens.  You will not be able to remove the assign button without removing the user's ability to assign the issue.

[Brian Sweet]

That's quite unfortunate. The lack of being able to customize built-in screens results in redundancy and confusion.

[Nic Brough -Adaptavist-]

I'm not sure about the "closed" screen - is that the transition screen you go through when closing an issue?  Transition screens can be customised.

[Brian Sweet]

The default "closed" option is just a transition, not a screen.

[Nic Brough -Adaptavist-]

If it's a transition, you can add a screen to it, and put whatever fields you need on the screen.

[Brian Sweet]

But it's a default transition that cannot be modified. Even if I create a new transition that's named the same ("Closed" in this case), the default "Closed" transition will be used.

[Nic Brough -Adaptavist-]

You can always modify the transitions, so I don't really understand what you mean there.  (The exceptions are the default workflow, but you can't add a second closed transition to that, and simplified workflows, which are a bit odd because you can modify them, but shouldn't)

[Brian Sweet]

Again, Jira comes with a "Closed" transition which simply changes the status to "Closed." This transition apparently can't be modified, so it is extremely limited and it can't be removed from the default transition bar. The same goes for the default "Assign" transition.

[Nic Brough -Adaptavist-]

You can remove that transition, or change the screen it uses.

The only workflow that you can't modify is the Jira default one (which you couldn't add "being delivered" to, so we know it's not that one)

[Brian Sweet]

How would you modify the default "Assign" and "Closed" transitions? They aren't even used in my custom workflow.

[Nic Brough -Adaptavist-]

Assign is an action, not a transition (a transition changes status, an action changes fields).

If your custom workflow does not have "closed" in it, then it is not the workflow that the issue you are looking at is using!  You want to be looking at the workflow that your issue is set up to use - have a look in project admin -> workflow scheme - that maps workflow to issue type.

[Brian Sweet]

My custom workflow already has a closed status in it which is triggered by a "Close Item" transition and screen. That is accessed under the "Workflow" dropdown.

[Nic Brough -Adaptavist-]

Yes, and the two buttons to the left of it, "closed" and "being delivered" are also transitions in your workflow. 

Those two just happen to be the first two available from the current status, there's nothing special about them.   You can change the number if items it starts grouping after, and re-order the transitions if you want, but that's another discussion.

At the moment, what you need to do is work out which workflow your issue is using, edit that workflow and then remove any redundant transitions (do you need 2 "close issue" type transitions?) and edit the screen associated with the "close" transition you want to keep.  There is no such thing as a transition you can't edit or remove, except in the Jira default workflow, which is fixed and definitely not the one you are using here.

[Brian Sweet]

Yet again, "Closed" is not a transition in my workflow. There is only one transition in my workflow that closes an issue, and it is not the one labeled as "Closed."

[Nic Brough -Adaptavist-]

But Closed is in the transitions shown for that issue.  So it is a transition in the workflow that this issue is using.  There is no other way it can be there.

So, either you are misreading your workflow, or you are looking at a different workflow than the one on this issue.

Try this:  Go to your workflow in the editor and look at the diagram.  Now go to the issue you took the screenshot from and click the "view workflow" button.  You will find that the second one has "Closed" going out of the current status, or a hanging black "all" box going into Closed.

[Brian Sweet]

I get what you're saying now :).

The "Closed" status in my workflow indeed has "allow all statuses to transition to this one" checked. The reason I set this is because I want some issues to skip the workflow and go straight to closed.

I've unchecked that, which removed "Closed" from the bar (which is perfect).

Now, can the "Assign" button be modified? I already have a custom "Assign members" transition and screen.

[Randy]

@Brian Sweetyou can also use ops-bar-sequence to hide the "Closed" transition at certain times too so that you can still maintain the All-> Closed transition.  That way you can allow issues to skip to closed at certain times without having to create a bunch of additional transitions for every case

[Nic Brough -Adaptavist-]

Ok, to be clear, the "Assign" button is about assigning issues (the one in the edit/comment/assign section in your screenshot).  It is not part of the workflow, and is not customisable.

But you also have a custom "Assign members" transition - this should be editable in the same way that your close transition(s) can be changed!

Sorry I didn't realise the All-> might be confounding this one earlier.  I've got so used to it, I forget to mention it sometimes.

[Brian Sweet]

@Randy Can that method be used to hide the "Assign" button? 

[Randy]

Unfortunately, no since only transitions appear on the ops bar.

With that said, you may want to just wait as Atlassian is redesigning the issue view screens and that button area will be undergoing a makeover.

[Brian Sweet]

Thanks goodness. Some additional customization for cloud users would be appreciated (and seemingly long overdue).

[Randy]

Agree.  Here's what it looks like and the blog post:

https://confluence.atlassian.com/jiracorecloud/the-new-jira-issue-view-938040503.html