First, Our JIRA admin left unexpectedly.
So far I have created the issue types, created and assigned an issue type scheme, created the screens, created and assigned the screen scheme. I then tried to assign the issue type screen scheme, but this still isn't working as desired.
Any advice/input would be GREATLY appreciated.
Well, high level, you:
Your description of what you did is ambiguous in some ways; if this overview doesn't help, then we'll need more specific information. Screen shots are always helpful as well.
We have a Legal JIRA project. I am attempting to to:
Create the Issue Type "Subpoena"
Create the Issue Type Scheme "Legal Subpoena" in order to Have Task and Subpoena on the Create screen
Create the screen "Legal Subpoena"
Create the Screen Scheme "Legal Subpoena"
Essentially I need mutually exclusive screens for Tasks and Subpoena's. Which screen shots can I grab for you?
So you have two Issue Types, "Task" and "Subpoena". Assuming the project key is "LEGAL", I would:
I use "Default" in the screen name, because it's not atypical to wind up with something like a "Legal Subpoena Resolve Screen" down the road, so you can select that screen during a transition. The "Default" helps to make the relative difference clear.
Re: the third and fourth bullet, if you want this screen just for Create Issue, just assign it to Create Issue, and assign some other screen (exclusive, shared, stock, whatever) to View/Edit.
The end result will be that, if you select "Task" when creating an issue in the LEGAL project, they'll get the "LEGAL Task Default Screen". Whereas if you select "Subpoena", you'll get the "LEGAL Subpoena Default Screen". Oh, speaking of... if you only map the screens to "Create Issue", then you'd want to name them:
Instead of "Default Screen". I'd only name them "Default Screen" if they are being used for all of Create/Edit/View.
Finally, that naming scheme is just my preference; I use "PROJECTKEY Type Operation Screen" whenever making a project/type specific screen, or "CATEGORY/GROUP Type Operation Screen" if it's shared amongst several projects, and just "KEY/CAT/GROUP Operation Screen" if it's not type specific. You may be able to derive a pattern in your existing deployment, or it may be whatever a given person chose at the time. Mostly, I think this is a good example of where the functional boundaries are; you are, of course, welcome to name them all whatever you like .
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
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