...
At this point we can make a copy of JIRA default screen and name it TTS Screen. Then remove all the fields except Summary, Issue type, Priority, Assignee, Reporter and Description. Then copy that screen configure and name them as above.
We'll configure them later when custom fields have been created.
...
TTS workflow steps and transitions:
KUVA
To create this workflow we need to:
...
Create screen scheme TTS Screen Scheme. Setup:
KUVA
Administration -> Sreen schemes
...
To put some of the fields on the same row, you first need to find out the field id of each field. You can do that on page Administration - Custom fields by selecting Configure and picking the id from the url. Then edit the options of the ordering field (eg. HF 1):
The Horizontal Fields custom field options take two parameters source and target. The source parameter accepts a comma separated list of html element ids. We have used the elements with the id %fieldId%FieldArea (for example customfield_10000FieldArea or assigneeFieldArea). The target parameter accepts a single html element id.
Hide fields
In Edit mode (normally every transition screen is thought of being in the Edit mode) TTS should hide some of the fields and in View mode its should hide other fields. The Field Hider custom field options take two parameters view and edit. Both of the parameters accept a comma separated list of html elemement ids same as the source parameter of the Horizontal Fields custom field options.
...
- TTS Screen - Opening: only fields Summary, Issue type
- TTS Screen - Resolve: as in TTS Screen + Customer info (on tab Customer), Fixer, Service info (SLA) (on tab Supplier), Supplier info (on tab Supplier)
- TTS Screen - Close: as in Resolve + Final ticket report
Complete screen
As shown in transition Resolve
Validators
Validators are connected to workflow transitions.
Administration - Workflows
All transitions
Required Fields Validator
Mark the fields you want to be required for this transition. Fields required like this are not shown as such in the user interface but if a user tries to perform the transition and the field has not been filled, the user will be notified of the unfilled required fields.
Problem Start/End Validator
Select the corresponding fields for Problem Start/End, Maintenance Window Start/End and Outages. Select if it's required that outage end or problem end is input.
Post fuctions
All transitions
Autofill problem start and end
Select the fields that correspond to the fields Manually editable Problem Start, Manually editable Problem End, Calculated Problem Start, Calculated Problem End, Outages.
Calculate total outage
Select the fields that correspond to the Outages field and the Total outage field.
Transitions Open ticket and Update Ticket (from Open to Open)
Auto-populate Next Action Due Date
Select the issue type for which you want to populate Next action due date from maintence window start if left empty. Then select the fields which correspond to the next action due date and maintenance window start.
Build the project
Projet setting
...
To use TTS in a project, you have to set TTS version for:
- Issue type scheme
- Issue type screen scheme
- Workflow scheme
- Permission scheme (recommended)
- Notification scheme (optional)
Permissions
Permission management of a TTS project is basically same than in any other JIRA project. Only thing you absolutely should do is disabling Edit permission. TTS workflow has a transition "Update ticket" we use for that. Using workflow transition enables post functions and more flexible event handling.
...