I have a couple of questions for you:
Hello Nic, Everyone,
1. Is there a way to remove/disable it then? Maybe replace the action with Edit issue in a new tab or at least View issue in a new tab? On some of the custom screens, I've created half of the options from that sidebar that are not used and will be just confusing for regular users.
Example use case: I made a custom meeting type task and screen. For that one (and many others) Components, Affects and Fix Versions and description field will be totally useless and might confuse users. In general, this view is just "persistently" coming up for me and taking the space I need for the board columns to be displayed neatly.
2. This is very disappointing, Doing 20 screens with 10-40 custom fields by hand is totally inefficient. I might want to partner up with a developer to build this script, but in that case I'd prefer to have it as a standalone plugin that would create those customized screens than a copying script. (aka I'd prefer to exclude original JIRA instance from the equation). Any advice on this?
3. If I understood well enough - if I have a custom screen with 3-4 tabs (relevant to transitions of that task) I'll need to make one custom screen with all of them together, and then for each transition separate screen for each tab. The all-tabs-together screens will be used on Create/Edit/View and separate ones on relevant transitions. What I wanted to do is to show Custom issue/Tab1 while issue is created, Custom Issue/Tab2 while it's in progress or blocked, Custom issue/Tab3 while issue is in review and so on......so not just at the moment of transition but whenever I click on view or edit the issue in those statuses.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events