-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
7.5.2, 7.7.1
-
7.05
-
1
-
Severity 2 - Major
-
1
-
Summary
The system fields Summary, Issue Type, and Reporter are automatically added to all issue type screen scheme screen tabs when created via server app using project-blueprint module.
Steps to Reproduce
- Follow https://developer.atlassian.com/server/jira/platform/creating-a-project-template/
- Modify the JSON configuration file and add
"issue-type-screen-scheme": { "name": "Issue Type Screen Scheme", "description": "This is the Issue Type Screen Scheme", "default-screen-scheme": "BugDefaultScreenScheme", "screens": [ { "key": "BugDefaultScreen", "name": "Bug -c/e- Screen", "tabs": [ { "name": "General", "fields": [ "issuetype" ] }, { "name": "Dates", "fields": [ "duedate" ] }, { "name": "Effort", "fields": [ "timetracking" ] } ] } ], "screen-schemes": [ { "key": "BugDefaultScreenScheme", "name": "Screen Scheme - Bug", "default-screen": "BugDefaultScreen" } ] }
Expected Results
Only the declared fields in the tabs will be shown
Notes
- When entering a value in one tab, the value is not even shared between the tabs.
- Tested in Jira versions 7.5.2 and 7.7.1
- relates to
-
JRASERVER-30649 Prevent duplicate form actions from happening - regression
- Closed
-
DEVHELP-1411 Loading...