The Configuring terminology documentation is currently focusing on what changes are expected with the new Terminology but not what's expected to remain the same, like:
- JQL searches (advanced search)
- REST API queries (use JQL, same as above)
- Custom field names (they remain Epic Name, Epic Link, Epic Color, etc)
We could make it clearer the Terminology feature in Jira works similar to a frontend/UI translation layer.
It changes only the Epic issue type name to the new terminology, leaving all Epic-related field names the way they are.
Even for the Epic issue type, only the output is translated. The input still requires the Epic keyword like in:
resolution = Unresolved and issuetype = Epic
| Basic search (works with Feature) | Advanced search (needs Epic) |
|---|---|
 |
 |
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-21390] Improve documentation on Configuring terminology to make the limitations clearer
| Fix Version/s | New: 8.13.0 [ 91997 ] | |
| Fix Version/s | New: 8.14.0 [ 92898 ] | |
| Fix Version/s | New: 8.15.0 [ 92947 ] | |
| Fix Version/s | New: 8.16.0 [ 94593 ] | |
| Fix Version/s | New: 8.17.0 [ 94802 ] | |
| Fix Version/s | New: 8.18.0 [ 95094 ] | |
| Fix Version/s | New: 8.19.0 [ 95693 ] | |
| Fix Version/s | New: 8.20.0 [ 95694 ] | |
| Fix Version/s | New: 8.21.0 [ 97590 ] | |
| Fix Version/s | New: 8.22.0 [ 98792 ] | |
| Fix Version/s | New: 9.0.0 [ 97892 ] | |
| Fix Version/s | New: 9.1.0 [ 99994 ] | |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
| Remote Link |
New:
This issue links to "Bugfixing & feedback processing in Jira DC: |
| Assignee | New: Oksana Levchuk [ bc878d9874ad ] |
| Attachment | New: screenshot-001.png [ 423496 ] | |
| Attachment | New: screenshot-002.png [ 423495 ] |