Details
-
Bug
-
Status: Done
-
Trivial
-
Resolution: Done
-
5.5.7.1-jira8
-
None
-
None
-
3.6
Description
Issue type field shows inconsistent issue types in Create Issue screen after language translated via User Profile. For example, using the code below:
import org.apache.log4j.Logger import org.apache.log4j.Level def log = Logger.getLogger("Test0 koep") log.setLevel(Level.DEBUG) import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.security.roles.ProjectRoleManager import static com.atlassian.jira.issue.IssueFieldConstants.ISSUE_TYPE def projectRoleManager = ComponentAccessor.getComponent(ProjectRoleManager) def allIssueTypes = ComponentAccessor.constantsManager.allIssueTypeObjects def user = ComponentAccessor.jiraAuthenticationContext.loggedInUser def issueTypeField = getFieldById(ISSUE_TYPE) def remoteUsersRoles = projectRoleManager.getProjectRoles(user, issueContext.projectObject)*.name def availableIssueTypes = allIssueTypes log.debug allIssueTypes issueTypeField.setFieldOptions(availableIssueTypes)
Steps to reproduce it
- Add the code above into initialiser behaviour config.
- Map a project with all issue types.
- Change language to German via User Profile
Issues types has filter to shows bug and epic issue types only.
Expected Behaviour
It should show all issue types.
Actual Behaviour
It gets filters.
Attachments
Issue Links
- duplicates
-
-
- Done
-
