Adama LIS Support
- Key: ALS
- Lead:
Tilahun Desalegn
- Project type: Software
- Category: None
- URL: http://www.example.com
System Default Field Configuration
Different issues can have different information fields. A field configuration defines how fields behave for the project, e.g. required/optional; hidden/visible.
The field configuration scheme defines which fields apply to this project. To change the fields used, you can select a different field configuration scheme, or modify the currently selected scheme.
This project uses only 1 field configuration.
Default Field Configuration Default
Shared by 2 projectsThese 5 issue types…
-
Story Default
-
Bug
-
Epic
-
Task
-
Sub-task
…use this field configuration
Name | Required | Renderers | Screens |
---|---|---|---|
Affects Version/s
|
Autocomplete Renderer | 57 screens | |
Assignee
|
133 screens | ||
Attachment
|
131 screens | ||
Business Value
Measurement of business value of a requirement. |
No screens | ||
Comment
|
Default Text Renderer | No screens | |
Component/S
|
22 screens | ||
Component/s
|
Autocomplete Renderer | 123 screens | |
Description
|
Default Text Renderer | 131 screens | |
Due Date
|
21 screens | ||
Environment
For example operating system, software platform and/or hardware specifications (include as appropriate for the issue). |
Default Text Renderer | 58 screens | |
Epic Color
Locked
Epic Color field for JIRA Software use only. |
Default Text Renderer | No screens | |
Epic Link
Locked
Choose an epic to assign this issue to. |
121 screens | ||
Epic Name
Locked
Provide a short name to identify this epic. |
Yes | Default Text Renderer | 63 screens |
Epic Status
Locked
Epic Status field for JIRA Software use only. |
1 screen | ||
External issue ID
External issue ID created by JIM during import process |
Default Text Renderer | 1 screen | |
Fix Version/s
|
Autocomplete Renderer | 121 screens | |
Flagged
Allows to flag issues with impediments. |
No screens | ||
Issue Raised Date
The date raised date |
1 screen | ||
Issue Solved by
The person who solved the issue |
1 screen | ||
Issue Title
The title for newly incoming issue |
Default Text Renderer | 1 screen | |
Issue Type
|
Yes | 142 screens | |
Issue created by
The person who is going to write the issue on JIRA |
1 screen | ||
Issue raised by
The person who raised the issue |
1 screen | ||
Labels
|
128 screens | ||
Lable/s
|
4 screens | ||
Letter Date
|
No screens | ||
Letter Number
|
Default Text Renderer | No screens | |
Linked Issues
|
135 screens | ||
Log Work
Allows work to be logged whilst creating, editing or transitioning issues. |
Default Text Renderer | 1 screen | |
Priority
|
131 screens | ||
Problem Description
The details of the issue faced by customers |
Default Text Renderer | 1 screen | |
Rank
Locked
Global rank field for JIRA Software use only. |
No screens | ||
Reporter
|
Yes | 141 screens | |
Requester
|
No screens | ||
Requester List
This field is dependent in each other. If you select the first drop down list the second becomes based on the first choice. |
No screens | ||
Requisite Number
|
Default Text Renderer | No screens | |
Resolution
|
21 screens | ||
Security Level
|
121 screens | ||
Solution description
The explanation which describes how the problem is solved. |
Default Text Renderer | 1 screen | |
Sprint
Locked
JIRA Software sprint field |
117 screens | ||
Story Points
Measurement of complexity and/or size of a requirement. |
No screens | ||
Summary
|
Yes | 143 screens | |
Test Case ID
|
Default Text Renderer | 4 screens | |
Time Tracking
An estimate of how much work remains until this issue will be resolved. The format of this is ' *w *d *h *m ' (representing weeks, days, hours and minutes - where * can be any number) Examples: 4d, 5h 30m, 60m and 3w. |
15 screens |