...
Equest Technologies Pvt. Ltd. |
Index
Topic Name | Page No. |
1. ISSUE TYPE
|
|
2. ISSUE TYPE SCHEME |
|
3. STATUS |
|
4. WORKFLOWS
|
|
5. WORKFLOW SCHEMES
|
|
Topic Name | Page No. |
6. CUSTOM FIELDS
|
|
7. SCREENS |
|
8. SCREEN SCHEME |
|
9. ISSUE TYPE SCREEN SCHEME |
|
JIRA Setup Documentation
ISSUE TYPE
How to create a new issue type:
- Log in as a user with the JIRA Administrator.
- Choose Choose the cog icon at top right of the screen, and then choose Issues. Select Issue Types to open the 'Issue Types' page, which lists all issue types.
- Click the Add Issue Type button to open the Add New Issue Type dialog box.
...
- Log in as a user with the JIRA Administrator.
- Choose the cog icon at top right of the screen, and then choose Issues. Select Issue Types to open the 'Issue Types' page, which lists all issue types.
- Click the Edit link (in the Operations column) for the issue type that you wish to edit. Edit
- Edit the Name, Description and/or Icon as described above for creating an issue type.
...
How to create a new issue type scheme:
- Go to the Issue Type Schemes tab (see above).
- Click the Add Issue Type Scheme button to open the Add Issue Type Scheme page.
- Enter the Scheme Name and Description for the new issue type scheme.
- To add issue types to your scheme, drag and drop an issue type from the Available Issue Types list on the right to the Issue Types for Current Scheme list on the left:
- If you need an issue type that does not currently exist, you can easily add this by using the Add New Issue Type button and dialog box. This will add the issue type to your JIRA system and also add it to Issue Types for Current Scheme list on the left.
- To reorder the issue types, drag and drop them into the preferred positions.
...
- Go to the Issue Type Schemes tab. Click the Associate link (in the Operations column) for the relevant Issue Type scheme.
- Using the multi-select Project box, choose the JIRA projects that you wish to apply your issue type scheme to.
- Click Associate button & all selected projects will change from their current scheme to selected scheme.
- Click the Associate button and all selected projects will change from their current scheme to the selected scheme.
...
- Log in as a user with the JIRA Administrator.
- Choose the cog icon at top right of the screen, and then choose Issues. Select Statuses to open the 'View Statuses' page, which lists all statuses, along with a form underneath to add a new status.
...
- A Transition is a link between two steps.
- A transition allows an issue to move from one step to another step.
- For an issue to be able to progress from one particular step to another, a transition must exist that links those two steps.
- A transition is a one-way link, so if an issue needs to move back and forth between two steps, two transitions need to be created.
- A user can execute a transition (i.e. move the issue through workflow) by clicking one of the available links.
...
- Log in as a user with the JIRA Administrator.
- Choose the cog icon at top right of the screen, and then choose Issues. Select Workflows to open the 'Workflows' page, which lists all existing workflows that have been defined in JIRA.
- Option 1 (Recommended Approach): Copy an existing workflow using the Copy link for an existing workflow.
- In the Copy Workflow dialog box, enter a name and description for your workflow.
- Click the Copy button. The workflow will open in edit mode, showing the layout of your copied workflow.
...
- Option 2 (for Advanced Administrators): Create a new workflow using the Add Workflow button:
- Enter a name and description for your workflow.
- Click the Add button.
The workflow opens in edit mode and contains a step called Open. If you are viewing your workflow in Diagram mode, you see an incoming transition called Create.
...
- Make sure that your workflow is in Diagram edit mode. Your workflow's existing steps as well as the lines and labels of transitions between these steps are shown in the workflow design area.
- Drag an available status from the Statuses panel list and drop it onto the workflow design area. A new step is added to your workflow.
...
- The Add New Step form appears below the list of steps. However, this will only be shown if the workflow is inactive or you are editing the draft of an active workflow.
- If no fields appear in this form, then all available statuses defined in your JIRA installation have been used in your workflow and you need to define a new status.
- Italicized transitions shown under Transitions (id) are 'common transitions'.
...
- In the Step Name field, type a short name for the step.
- In the Linked Status field, select the status that corresponds to this step. Each status can only correspond to one step in each workflow. Hence, if all statuses are linked to steps in this workflow.
- Click the Add button. Your new step appears in your workflow's list of steps in Text edit mode.
- Editing a step
- Log in as a user with the JIRA Administrator.
- Choose the cog icon at top right of the screen, and then choose Issues. Select Workflows to open the 'Workflows' page, which lists all existing workflows that have been defined in JIRA.
- Click the Edit link next to the workflow that you wish to add a step to.
- Make sure Text button is selected so that your workflow appears in Text edit mode. A list of existing steps that comprise the workflow and each step's Linked Status and Outgoing Transitions (under Transitions (id)) is shown.
...
- Add Transition - to add an Outgoing Transition to that step.
- Delete Transitions - to delete one or more Outgoing Transitions of that step. This link is only available if the step has at least one outgoing transition.
- Edit - to edit the step's Step Name or Linked Status.
- View Properties - to view and edit the step's Properties.
- Delete Step - to do just that. This link is only available if step has no Incoming Transitions.
Alternatively, you can access a step's View Workflow Step page to edit the step. To access this page, click the name of the step you wish to edit in the Step Name (id) column (e.g. Open). The step's View Workflow Step page is displayed.
On View Workflow Step page, the following information is shown about the step:
...
Using 'Diagram' edit mode to set the step's property:
- Make sure that your workflow appears in Diagram edit mode. Your workflow's existing steps are shown in workflow design area.
- Move mouse pointer over relevant step & click cog icon that appears to right of step to reveal popup menu.
- From the popup menu, select Issue Editable to remove the tick from that menu item. This action sets the step's jira.issue.editable property and its value to false.
...
Many of JIRA's default screens are used in a copied system workflow (above) and named after the transitions they are used in (e.g. Start Progress and Resolve Issue).
- Clone Transition, then in the Transition To Clone field, select transition you wish to copy.
Copying an existing transition creates a new independent copy of a transition, which does not result in a 'common transition'.
- If you choose Use Common Transition, select an existing transition (currently used in your workflow which also leads to your Destination Step) from the Transition To Reuse dropdown list.
...
- No view for transition — choose this if you do not need to prompt the user for input before the transition is executed (i.e. the transition will occur instantly when the user clicks the transition).
- The name of a screen that will be shown to users, asking for input before the transition is executed. You can choose one of JIRA's default screens or any other screen you have created. If no existing screen is suitable, you may wish to create a new screen for the transition.
- Editing or deleting an existing transition of a workflow:
- Log in as a user with the JIRA Administrator.
- Choose the cog icon at top right of the screen, and then choose Issues. Select Workflows to open the 'Workflows' page, which lists all existing workflows that have been defined in JIRA.
- Click the Edit link next to the workflow you wish to add a transition to.
- Use either the Diagram or Text edit mode to add the transition to the workflow.
- Editing or deleting an existing transition of a workflow:
Using 'Diagram' edit mode to edit or delete the transition
- Make sure that your workflow appears in Diagram edit mode. Your workflow's existing steps as well as the lines and labels of transitions between these steps are shown in workflow design area.
- Move the mouse pointer over the relevant transition label and click the cog icon that appears to the right of the label to reveal a popup menu.
- From the popup menu, you can:
...
- On the left of the Transition page:
- Transition View — the screen (usable globally) that your specific workflow transition uses. If your workflow transition does not require a view (i.e. no screen has been specified), then none - it will happen instantly is shown.
- In the Workflow Browser section:
- Originating Steps — steps whose Outgoing Transition is the transition you are currently viewing.
- Destination Step — the step whose Incoming Transition is the transition you are currently viewing.
- On the Transition page, you can:
...
Transition | Conditions | Validators | Post Functions | Transition View |
Create Issue (1) | Only users with Create Issues permission can execute this transition. |
|
|
|
Start Progress (11) |
|
|
| ABM_ENH_StartProgress |
Hold (21) |
| Required fields: Remarks |
| ABM_ENH_HOLD_ABANDON |
Abandon (31) |
| Required fields: Remarks | The Resolution of issue will be set to Abandoned. | ABM_ENH_HOLD_ABANDON |
Hold (41) |
| Required fields: Remarks |
| ABM_ENH_HOLD_ABANDON |
Abandon (51) |
| Required fields: Remarks | The Resolution of issue will be set to Abandoned. | ABM_ENH_HOLD_ABANDON |
Close (61) | All sub-tasks must have one of following statuses to allow parent issue transitions: Closed. | Required fields: Actual Size, Units (FP,LOC, complexity) | The Resolution of the issue will be set to Fixed. | ABM_ENH_CLOSE |
Start Progress (71) |
| Required fields: Actual Start Date, Remarks |
| ABM_ENH_StartProgress |
Abandon (81) |
| Required fields: Remarks | The Resolution of issue will be set toAbandoned | ABM_ENH_HOLD_ABANDON |
ABM-Audit_Cycle
Transition | Conditions | Validators | Post Functions | Transition View |
Create Issue (1) | Only users with Create Issues permission can execute this transition |
|
|
|
Plan (11) | Only users in project role Auditor coordinator can execute this transition | Required fields: Remarks |
| ABM-Adding_UpdatingProjectsToAuditCycle |
Cancel (51) | Only users in project role Auditor coordinator can execute this transition |
|
| ABM-CancellingAudits |
Start Progress (21) | Only users in project role Auditor coordinator can execute this transition |
|
| ABM-CancellingAudits |
Cancel (41) | Only users in project role Auditor coordinator can execute this transition |
|
| ABM-CancellingAudits |
Close (31) | Only users in project role Auditor coordinator can execute this transition |
|
| ABM-CancellingAudits |
...
Transition | Conditions | Validators | Post Functions | Transition View |
Create Issue (1) | Only users with Create Issues permission can execute this transition |
|
|
|
Reject (11) | Only users in project role Auditee can execute this transition. |
|
| ABM-CancellingAudits |
Start Progress (21) | Only users in project role Auditee can execute this transition |
|
| ABM-UpdatingAuditFindingsForAuditObservations |
Close (31) | Only users in project role Auditee can execute this transition. |
| The Resolution of the issue will be set to Fixed. | ABM-CancellingAudits |
ABM-Audit_workflow
Transition | Conditions | Validators | Post Functions | Transition View |
Create Issue (1) | Only users with Create Issues permission can execute this transition |
|
|
|
Conduct (11) | Only users in project role Auditor can execute this transition. |
|
| ABM-UpdatingAuditFindings |
Cancel (21) | Only users in project role Auditor can execute this transition | Required fields: Remarks |
| ABM-CancellingAudits |
Close (31) | Only users in project role Auditor can execute this transition. | Required fields: Remarks | The Resolution of the issue will be set to Fixed. | ABM-CancellingAudits |
...
Transition | Conditions | Validators | Post Functions | Transition View |
Create Issue (1) | Only users with Create Issues permission can execute this transition |
|
|
|
Start Progress (11) | Only assignee of issue can execute this transition. |
| The Response Time of the issue will be set to %%CURRENT_DATETIME%% | ABM_SER_strt_progress |
Not in Scope (51) | Only assignee of issue can execute this transition. |
|
| ABM_Ser_CLOSE_OPEN |
Fix (21) | Only assignee of issue can execute this transition. |
| The Resolution of issue will be set to Fixed. The Resolution Time of the issue will be set to %%CURRENT_DATETIME%%. | ABM_Ser_INprog_fix |
Close and Verify (31) | Only assignee of issue can execute this transition. |
|
| ABM_Ser_CLOSE_OPEN |
Re-Open (71) | Only assignee of issue can execute this transition. |
| The contents of field Resolution will be purged. | ABM_Ser_CLOSE_OPEN |
Not in Scope (81) | Only assignee of issue can execute this transition. |
| The contents of field Resolution will be purged. | ABM_Ser_CLOSE_OPEN |
Close (41) | Only assignee of issue can execute this transition. |
|
| ABM_Only_remark |
Re-Open (61) | Only assignee of issue can execute this transition. |
| The contents of field Resolution will be purged | ABM_Ser_CLOSE_OPEN |
ABM-SQARisk
Transition | Conditions | Validators | Post Functions | Transition View |
Create Issue (1) | Only users with Create Issues permission can execute this transition |
|
|
|
Close (11) | Only users in project role SQA can execute this transition. |
|
| ABM-SQK_riskUpdate |
Update (41) | Only users in project role SQA can execute this transition. | Required fields: Remarks |
| ABM-Risk_update_Over all |
Close (31) | Only users in project role SQA can execute this transition. |
| The Resolution of the issue will be set to Fixed. | ABM-Risk_update |
Re-Open (21) | Only users in project role SQA can execute this transition. |
| The contents of field Resolution will be purged. | ABM-Risk_update |
Close (51) | Only users in project role SQA can execute this transition. |
| The Resolution of the issue will be set to Fixed. | ABM-Risk_update |
...
- Log in as a user with the JIRA Administrator.
- Create a workflow scheme or find an existing workflow scheme.
- Configure the workflow scheme to use your workflow, i.e. add the workflow to the workflow scheme. See Configuring Workflow Schemes for instructions.
- Associate your workflow scheme with a project, as described in the Associating a workflow scheme with a project section.
Associating a workflow scheme with a project
- Log in as a user with the JIRA Administrator.
- Choose the cog icon at top right of the screen, and then choose Projects. The 'Projects Summary' page is displayed.
...
WORKFLOW SCHEMES
A workflow scheme defines a set of associations – or mappings – between a workflow and an issue type. Workflow schemes are associated with a project and make it possible to use a different workflow for every combination of project and issue type.
Adding a workflow scheme
- Log in as a user with the JIRA Administrator.
- Choose the cog icon at top right of the screen, and then choose Issues. Select 'Workflow Schemes' to open the 'Workflow Schemes' page.
...
- Click the Add Workflow Scheme button.
- Enter the Name and Description of the new workflow scheme.
- Click the Add button. The new workflow scheme is created.
- Next to that, configure workflows for a workflow scheme.
Configuring workflows for a workflow scheme
If your scheme is associated with a project, follow the instructions in "Configuring a workflow scheme associated with a project". Otherwise, follow the instructions in "Configuring a workflow scheme outside of a project".
Configuring a workflow scheme associated with a project
- Log in as a user with the JIRA Administrator.
- Choose the cog icon at top right of the screen, and then choose Projects.
- Click Workflows on left of Project Summary page. The Workflows page is displayed, indicating current workflow scheme used by the project.
...
- Click Associate to begin the migration process. Each issue has to be in a valid status. The valid statuses for an issue are defined by its workflow. This means that when changing a workflow, you may need to tell JIRA the status for specific issues after the change.
- A screen displays that indicates the progress of migrating all the project's issues to the updated scheme's workflows.
Click Acknowledge to finish the process. A message displays letting you know that 'your workflows have been published.'
Operation
Instructions
Add a workflow to the scheme
Click Add Workflow & select 'Choose From Marketplace' or 'Add Existing'. [Choose from Marketplace lets you import a workflow from the Atlassian Marketplace.]
Select the desired workflow and issue types.Edit a workflow
Hover over the desired workflow and click the Edit button.
Note: Edit button only displays if you have edit permission. You can only edit system workflow if you are viewing it in JIRA's default workflow scheme.Remove a workflow from scheme
Click cog icon for desired workflow and select Remove this workflow.
Change issue type associated with workflow
1. Click the Assign link under Issue Types for the desired workflow.2. Select the desired issue types in the dialog that appears.3. Click Finish.
View the text-based representation of a workflow
Hover over the desired workflow and click the View as Text link.
Change workflow scheme associated with project
Click the Switch Scheme button next to the scheme name.
Configuring a workflow scheme outside of a project
You can use this procedure to edit any workflow scheme in the system, including those shared by multiple projects. The workflow scheme can be either active or inactive.
Before you begin:
If your workflow scheme is associated with a project, you may want to follow the instructions above instead. When a workflow scheme is used by more than one project, you must use this configuration method.
When a workflow scheme is active, it creates a 'draft workflow scheme' when you edit it.
To configure the workflow scheme that is not associated with a project:- Log in as a user with the JIRA Administrator.
- Choose the cog icon at top right of the screen, and then choose Issues. Select Workflow Schemes to open the 'Workflow Schemes' page.
- Click the Edit link under the Operations column for the desired workflow.
- Edit your workflow scheme as described in the table below.
- If your workflow is active, you need to publish it to make your changes active.
Operation | Instructions |
Add a workflow to the scheme | 1. Click Add Workflow and select 'Choose From Marketplace' or 'Add Existing'. |
Remove a workflow from the scheme | Click the Remove link in the Operations column. |
Change the issue types associated with a workflow | 1. Click the Assign link under Issue Types for the desired workflow.2. Select the desired issue types in the dialog that appears.3. Click Finish. |
View representation of a workflow | Click either the Text or Diagram link next to the Workflow name. |
Remove issue type from scheme | Click the x next to the name of the issue type to remove it. |
...
- Log in as a user with the JIRA Administrator.
- Choose the cog icon at top right of the screen, & then choose Issues. Select Workflow Schemes to open the 'Workflow Schemes' page
Operation | Instructions |
Edit the name and description of a workflow scheme | Click the Edit link. Use inline edit mode – click in the associated field – to update the name and description. |
Copy a workflow scheme | Click the Copy link. A copy of workflow scheme is created with prefix 'Copy of (name of current workflow)' and placed in inactive workflow schemes. |
Delete a workflow scheme | Click the Delete link and confirm the deletion. |
...
- Log in as a user with the JIRA Administrator.
- Choose the cog icon at top right of the screen, and then choose Issues. Select Fields > Custom Fields to open the 'Custom Fields' page.
- Click the Add Custom Field button on to open the Create Custom Field: Choose the field type (Step 1 of 2) page.
...
- Select the appropriate type of field for your custom field.
- Click the Next button to open the Create Custom Field - Details (Step 2 of 2) page.
...
- Complete the Field Name (custom field's title) and Field Description.
- Select an appropriate Search Template. Pre-configured search templates are available for each shipped custom field type.
- Select one or any number of 'Issue Types' to which this custom field will be available. Alternatively, select 'Any issue type' to make the custom field available to all Issue Types.
- Select the applicable context, that is, the 'Project(s)' to which the custom field will be available. Alternatively, select 'Global context' to make the custom field available to all projects.
- If issue types were chosen, the custom field will only appear for those issue types for the selected project(s).
- Click the 'Finish' button. This will bring you to the screen association page:
...
- Select a screen, or screen tab, on which to display your newly created custom field. You must associate a field with a screen before it will be displayed. New fields will be added to the end of a tab.
- Click the 'Update' button. You will return you to the View Custom Fields page, which displays a summary of all custom fields in JIRA system.
- You can edit, delete or configure custom fields here. This page is also directly accessible from the menu bar to the left of all Administration pages.
Editing a Custom Field Details
Editing a custom field allows you to change its Name (label), Description (Help text) and Search Template.
- Log in as a user with the JIRA Administrator.
- Choose the cog icon at top right of the screen, and then choose Issues. Select Fields > Custom Fields to open the 'Custom Fields' page.
- Locate the relevant custom field and choose cog icon > Edit.
...
- Locate the relevant custom field and choose cog icon > Edit.
Modify the desired fields and click on Update.
Fields
Use
Name
Name is the label that appears to the left of the custom field when it is displayed to a user.
Description
Description is the Help text that appears below the custom field when it is displayed in the Simple Search column.
Search Templates
Search Templates are responsible for indexing a custom field as well as making it searchable via Simple Search & Advanced Search
NOTE: Custom fields are not searchable via Quick Search.- Note that changing a custom field searcher may require a re-indexing.
...
- Log in as a user with the JIRA Administrator.
- Choose the cog icon at top right of the screen, and then choose Issues. Select Fields > Custom Fields to open the 'Custom Fields' page.
- Locate the relevant custom field and choose cog icon > Configure.
- Locate the relevant context (there will usually only is one, named 'Default Configuration Scheme for ...') and click the Edit Configuration link.
- Under 'Choose applicable issue types', select the issue type(s) to which you want this Default Value and Options to apply. You can select any issue types if you wish.
- Under 'Choose applicable contexts', select the project(s) to which you want this Default Value and Options to apply. Note that this will apply to only issues with the selected issue type(s) as above.
...
- (For a Select List or Multi-Select List) Select the appropriate default value from the drop-down list.
- (For a Cascading Select List) Select the appropriate default values from the drop-down lists (one for each level).
- (For a Date field) Specify a date, or tick the check-box to make the current date the default.
- (For other types of fields) Type the appropriate default values from the drop-down lists (one for each level).
- The 'Edit Custom Field Options' page will display:
...
- Log in as a user with the JIRA Administrator.
- Choose the cog icon at top right of the screen, and then choose Issues. Select Fields > Custom Fields to open the 'Custom Fields' page.
- Click the Add Custom Field button on to open the Create Custom Field: Choose the field type (Step 1 of 2) page.
- Select the Free Text type of field for new custom field.
- Click the Next button to open the Create Custom Field - Details (Step 2 of 2) page.
...
- Complete the Field Name (custom field's title) and Field Description.
- Select one or any number of 'Issue Types' to which this custom field will be available. Alternatively, select 'Any issue type' to make the custom field available to all Issue Types.
- Select the applicable context, that is, the 'Project(s)' to which the custom field will be available. Alternatively, select 'Global context' to make the custom field available to all projects.
- Click the 'Finish' button. This will bring you to the screen association page:
...
- Log in as a user with the JIRA Administrator.
- Choose the cog icon at top right of the screen, and then choose Issues. Select Fields > Custom Fields to open the 'Custom Fields' page.
- Click the Add Custom Field button on to open the Create Custom Field: Choose the field type (Step 1 of 2) page.
- Select the Free Text type of field for new custom field.
- Click the Next button to open the Create Custom Field - Details (Step 2 of 2) page.
...
- Complete the Field Name (custom field's title) and Field Description.
- Select one or any number of 'Issue Types' to which this custom field will be available. Alternatively, select 'Any issue type' to make the custom field available to all Issue Types.
- Select the applicable context, that is, the 'Project(s)' to which the custom field will be available. Alternatively, select 'Global context' to make the custom field available to all projects.
- Click the 'Finish' button. This will bring you to the screen association page:
...
- Log in as a user with the JIRA Administrator.
- Choose the cog icon at top right of the screen, and then choose Issues. Select Fields > Custom Fields to open the 'Custom Fields' page.
- Click the Add Custom Field button on to open the Create Custom Field: Choose the field type (Step 1 of 2) page.
- Select the Number Field type of field for new custom field.
- Click the Next button to open the Create Custom Field - Details (Step 2 of 2) page.
...
- Complete the Field Name (custom field's title) and Field Description.
- Select one or any number of 'Issue Types' to which this custom field will be available. Alternatively, select 'Any issue type' to make the custom field available to all Issue Types.
- Select the applicable context, that is, the 'Project(s)' to which the custom field will be available. Alternatively, select 'Global context' to make the custom field available to all projects.
- Click the 'Finish' button. This will bring you to the screen association page:
...
- Log in as a user with the JIRA Administrator.
- Choose the cog icon at top right of the screen, and then choose Issues. Select Fields > Custom Fields to open the 'Custom Fields' page.
- Click the Add Custom Field button on to open the Create Custom Field: Choose the field type (Step 1 of 2) page.
- Select the Date Time type of field for new custom field.
- Click the Next button to open the Create Custom Field - Details (Step 2 of 2) page.
...
- Complete the Field Name (custom field's title) and Field Description.
- Select one or any number of 'Issue Types' to which this custom field will be available. Alternatively, select 'Any issue type' to make the custom field available to all Issue Types.
- Select the applicable context, that is, the 'Project(s)' to which the custom field will be available. Alternatively, select 'Global context' to make the custom field available to all projects.
- Click the 'Finish' button. This will bring you to the screen association page:
...
- Log in as a user with the JIRA Administrator.
- Choose the cog icon at top right of the screen, and then choose Issues. Select Fields > Custom Fields to open the 'Custom Fields' page.
- Click the Add Custom Field button on to open the Create Custom Field: Choose the field type (Step 1 of 2) page.
- Select the Radio Button type of field for new custom field.
- Click the Next button to open the Create Custom Field - Details (Step 2 of 2) page.
...
- Complete the Field Name (custom field's title) and Field Description.
- Select one or any number of 'Issue Types' to which this custom field will be available. Alternatively, select 'Any issue type' to make the custom field available to all Issue Types.
- Select the applicable context, that is, the 'Project(s)' to which the custom field will be available. Alternatively, select 'Global context' to make the custom field available to all projects.
- Click the 'Finish' button. This will bring you to the screen association page:
...
- Click Sort alphabetically to automatically re-order the options alphabetically.
- Click the arrows in the Order column, or specify a number and click the Move button, to re-order the options manually.
- Click Edit to change the text of an option.
- Click Disable to hide an option so that it is no longer available for selection.
- Click Delete to remove an option.
...
- Log in as a user with the JIRA Administrator.
- Choose the cog icon at top right of the screen, and then choose Issues. Select Fields > Custom Fields to open the 'Custom Fields' page.
- Click the Add Custom Field button on to open the Create Custom Field: Choose the field type (Step 1 of 2) page.
- Select the User Picker type of field for new custom field.
- Click the Next button to open the Create Custom Field - Details (Step 2 of 2) page.
...
- Complete the Field Name (custom field's title) and Field Description.
- Select one or any number of 'Issue Types' to which this custom field will be available. Alternatively, select 'Any issue type' to make the custom field available to all Issue Types.
- Select the applicable context, that is, the 'Project(s)' to which the custom field will be available. Alternatively, select 'Global context' to make the custom field available to all projects.
- Click the 'Finish' button. This will bring you to the screen association page:
...
- Log in as a user with the JIRA Administrator.
- Choose the cog icon at top right of the screen, and then choose Issues. Select Fields > Custom Fields to open the 'Custom Fields' page.
- Click the Add Custom Field button on to open the Create Custom Field: Choose the field type (Step 1 of 2) page.
- Select the Select List type of field for new custom field.
- Click the Next button to open the Create Custom Field - Details (Step 2 of 2) page.
...
- Complete the Field Name (custom field's title) and Field Description.
- Select one or any number of 'Issue Types' to which this custom field will be available. Alternatively, select 'Any issue type' to make the custom field available to all Issue Types.
- Select the applicable context, that is, the 'Project(s)' to which the custom field will be available. Alternatively, select 'Global context' to make the custom field available to all projects.
- Click the 'Finish' button. This will bring you to the screen association page:
...
- Click Sort alphabetically to automatically re-order the options alphabetically.
- Click the arrows in the Order column, or specify a number and click the Move button, to re-order the options manually.
- Click Edit to change the text of an option.
- Click Disable to hide an option so that it is no longer available for selection.
- Click Delete to remove an option.
...
- Log in as a user with the JIRA Administrator.
- Choose the cog icon at top right of the screen, and then choose Issues. Select Fields > Custom Fields to open the 'Custom Fields' page.
- Click the Add Custom Field button on to open the Create Custom Field: Choose the field type (Step 1 of 2) page.
- Select the Multi Select List type of field for new custom field.
- Click the Next button to open the Create Custom Field - Details (Step 2 of 2) page.
...
- Complete the Field Name (custom field's title) and Field Description.
- Select one or any number of 'Issue Types' to which this custom field will be available. Alternatively, select 'Any issue type' to make the custom field available to all Issue Types.
- Select the applicable context, that is, the 'Project(s)' to which the custom field will be available. Alternatively, select 'Global context' to make the custom field available to all projects.
- Click the 'Finish' button. This will bring you to the screen association page:
...
- Click Sort alphabetically to automatically re-order the options alphabetically.
- Click arrows in Order column, or specify a number and click Move button, to re-order options manually.
- Click Edit to change the text of an option.
- Click Disable to hide an option so that it is no longer available for selection.
- Click Delete to remove an option.
...
- Log in as a user with the JIRA Administrator.
- Choose the cog icon at top right of the screen, and then choose Issues. Select Screens to open the 'View Screens' page, which lists all screens that have been defined in JIRA.
- Click the Add New Screen button to open the Add New Screen dialog box.
...
- Name - Enter a short phrase that best describes your new screen.
- Description - Enter a sentence or two to describe the situations screen will be used.
- Click the Add button to add your new screen to JIRA.
...
- Log in as a user with the JIRA Administrator.
- Choose the cog icon at top right of the screen, and then choose Issues. Select Screens to open the 'View Screens' page, which lists all screens that have been defined in JIRA.
- Click the Edit link next to the appropriate screen.
- You will now be directed to the Edit Screen page where you can edit the name and/or description of the Screen.
- After Editing screen name and/or description click on Update to save the changes.
...
- Log in as a user with the JIRA Administrator.
- Choose the cog icon at top right of the screen, and then choose Issues. Select Screens to open the 'View Screens' page, which lists all screens that have been defined in JIRA.
- Click the Copy link next to the appropriate screen.
- You will now be directed to the Copy Screen page where you can edit the name and/or description of the Screen.
- After defining screen name and/or description click on Copy to save the changes.
...
- Log in as a user with the JIRA Administrator.
- Choose the cog icon at top right of the screen, and then choose Issues. Select Screens to open the 'View Screens' page, which lists all screens that have been defined in JIRA.
- Click the Configure link to open the Configure Screen page for that screen.
Operation | Instructions |
Add tab | Click Add Tab. Enter the name of the new tab in the dialog that appears and click Add. |
Move tab | Hover over the dotted part of the tab (next to the tab name) and drag the tab to the desired position. |
Rename tab | 1. Hover over the tab name and click the pencil icon.2. Enter the new name and click OK. |
Delete tab | Hover over the tab name and click the X. |
Add field | 1. Click the tab that you want to add the field to.2. Type the name of the field in the dropdown displayed at the bottom of the current fields. Field suggestions will appear as you type. 3. Click Add Field to add it to the current tab. |
Move field | Hover over the dotted part of the field (next to the field name) and drag the field to the desired position.Move a field to a different tab by dragging it to the name of the tab and dropping it. |
Delete field | Hover over the field and click the Delete button that appears. |
Activating a screen
To make a Screen available to users, you can either:
...
- Log in as a user with the JIRA Administrator.
- Choose the cog icon at top right of the screen, and then choose Issues. Select Screens > Screen Schemes to open the 'View Screens Schemes' page.
- Click the Add New Screen Scheme button on the View Screen Schemes page.
- Fill out the details for the new screen scheme on the form that is displayed.
Note: default screen is used for issue operations that do not have screen associated with them.
Editing a Screen Scheme's details
- Log in as a user with the JIRA Administrator.
- Choose the cog icon at top right of the screen, and then choose Issues. Select Screens > Screen Schemes to open the 'View Screens Schemes' page.
- The View Screen Schemes page is displayed. Click Edit next to desired screen scheme.
...
- You will now be directed to the Edit Screen Scheme page where you can edit the Screen Scheme's name and description and the Screen that is associated with the Default Entry of the scheme.
Deleting a Screen Scheme
Note that screen schemes that are associated with an Issue Type Screen Scheme cannot be deleted. You will first need to edit the Issue Type Screen Scheme and remove the Screen Scheme.
- Log in as a user with the JIRA Administrator.
- Choose the cog icon at top right of the screen, and then choose Issues. Select Screens > Screen Schemes to open the 'View Screens Schemes' page.
- The View Screen Schemes page is displayed. Click the Delete link next to the desired Screen Scheme. You will be prompted to confirm your deletion.
Copying a Screen Scheme
- Log in as a user with the JIRA Administrator.
- Choose the cog icon at top right of the screen, and then choose Issues. Select Screens > Screen Schemes to open the 'View Screens Schemes' page.
- The View Screen Schemes page is displayed. Click Copy next to the Screen Scheme you wish to copy.
- You will now be directed to the Copy Screen Scheme page. Enter the name and description of the new Screen Scheme and click the Copy button.
Configuring a Screen Scheme
Associating a screen with an issue operation
...
- Do the following:
- Select the Issue Operation with which you wish to associate a Screen.
- Select the desired Screen.
Important Notes
- There can only be one association for an issue operation per Screen Scheme. If all operations have been associated with a Screen, use the Edit link next to each operation to change the Screen it is associated with.
- If an issue operation does not have a specific mapping to a Screen, the screen that is associated with the Default entry will be used for that operation. The Default entry cannot be deleted from a Screen Scheme. Click Edit next to the Default entry to change the Screen that is associated with it.
- The View Issue operation only allows you to control the layout of custom fields in the middle of the View Issue page. It ignores all the non-custom fields on the Screen.
...
- Log in as a user with the JIRA Administrator.
- Choose the cog icon at top right of the screen, and then choose Issues. Select Screens > Issue Type Screen Schemes to open the 'View Issue Type Screens Schemes' page.
- Click the Copy link next to the field screen you wish to copy, which opens the Copy Issue Type Screen Scheme page.
- Enter name and description of new Issue Type Screen Scheme and click Copy button.
...
Issue Type | Screen Scheme |
Audit | ABM-Audit-Only |
Audit Cycle | ABM-Audit_Cycle |
Audit Observation | ABM-AuditObservation |
Bug | ABM-Defect_management |
Improvement | ABM-Enhancement |
Enhancement Sub-Task | ABM_ENH_SUB |
Issue Management | ABM-IssueManagement |
Risk | ABM-RiskMgmt |
Over All Risk | ABM-SQA-Rsk |
PI | ABM-PI_Screen scheme |
Service | ABM_Sevice_mg |
Default | Aditya Birla Minac screen scheme |