I've managed to set up a quite default workflow with everything attached etc, but I didn't really inderstand what I was doing. I know somehow what is what, but I just don't get it on how to connect everything properly.
I have to make a new one now (so including all the screens and field configuration etc) but I just don't get it how it works and where to start. Especially that last bit. It contains a whole new workflow and I have different issue types that have to have different screens and some issue types have to use an existing workflow.
I am reading again all the info on the Atlassian site, but I was wondering if anybody could explain it more simple and short on how it works and where to start and which part to do before the other etc.
Hope it's possible...!
p.s. how should I interprete "mapping"? English is not my mother language. I understand associating, but what's the difference with mapping then?
(I have the old version from JIRA, don't know if that's Core or Software, sorry)
I faced the same question and created this: https://answers.atlassian.com/questions/32985938. Hope it will help.
To make it simple:
Issue type scheme defines which issue types a allowed into given poject. And all other connect issue type in the given project with: Screens, workflows and field configuration.
About mapping. Lets see issue type Bug. For different situation you could need have different workflows for this issue type. This assotiation of issue type to specified workflow for given project is called mapping.
I have the thought that you should work backwards? Defining which fields you want on which screen, and then look which screens can be put together in a screen scheme to have a 1 thing you can attach to an operation.
Hmm, which now looks like you should take an operation and see what you want for fields on the associated screen for it...
In the examples, Create, View and Edit are Operations. Create is a screen, but Edit is the same and View probably to (don't know what that does).
When you have transitions in your workflow, you need screens for that too, right?
Create - is a screen, which an user will see when creates an issue. View - is defines which fields will be shown when issue is just open Edit - is a screen which appears when an user press "Edit button", namely - field list, that user with edit right coud edit. For any transition you can also specify any screen. For example, if you have a bug and a user have to specify the date when it will be fixed.In this case you need to create a sreen with a filed for this date and assign this screen to a transition. But if an user do not need do fill any fields just do not assing any screen for transition.
You have probably found this section of the Atlassian documentation site (https://confluence.atlassian.com/display/CONFEVAL/1.+Getting+Started)
Whilst there are a little dated in terms of the version of JIRA being demonstrated the principles are all sound and it can provide you with a good foundation.
Mapping is really the same as associating in the context of JIRA it just means that what you are doing is taking a configuration and saying when to use those particular configurations. For example you might map a single workflow to multiple issue types or have unique workflows for each issue type. This is the mapping you set up in the scheme.
Hope this helps
Vera, issue type schemedefines which issue types are allowed into a projecr. Other schemes assotiate something with these types. Workflow scheme assotiate a workflow with each issue type, screen scheme assotiate screens. Is allows you to have one issue type, for example Bug, and different workflow into different projects. Is it clear?
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new 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