Hello! I am trying to add a sub task called subdefect to a project. I added it in the issues area in administration, but I can't see it in the project. What am I doing wrong? It's a team managed project.
@Clare Lawson, currently, Team-managed projects only allow you to add "standard" issue types. See this post: https://community.atlassian.com/t5/Jira-questions/I-am-trying-to-add-a-sub-task-issue-type-to-my-team-managed/qaq-p/1892862.
I just checked within my instance and, as far as I can tell, this is still the case.
Agree, hierarchy of issue types cannot be modified in Team Managed projects, so creating any new issues type is treated similar to task.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm on a company managed project, but when I went to Jira Settings > Issues, then clicked "add issue type" (top right of screenshot) the popup menu allowed me to add a subtask type. I'm a relatively new Jira Admin so not sure how other settings would impact this, but hopefully it helps a little.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Clare Lawson I've just spun test projects now in my sandbox to test both Kanban and Scrum screen recordings are attached for both project types.
Both are team managed software projects.
Can you confirm the permission sets on the project in question? As for both test projects the subtask appeared with no additional configuration steps
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you. I can make it an issue type but I wanted it to be a subtask, not a regular issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Team managed projects are limited to the issue types created within the project itself, if you create an issue type at the Jira admin level, it will only be available for company managed projects. Same goes for custom fields, Statuses, etc. Anything in a team managed project is limited to what you have in the project itself, system settings won't be available.
The team managed project comes with a Subtask issue type that you can update the name to Subdefect if you would like, but the Team managed projects will not allow you to create a different sub task issue type.
I usually recommend that admins don't allow team managed projects as the admin of the project can change any part of the project at any time, auditors usually frown upon this behavior. Another benefit of using Company managed projects is they are more robust in what you can do with them. For instance setting up different sub task level issues. The boards in a company managed project give you more info and provide more flexibility as well and the reporting is much more detailed.
Company managed projects allow you to set up permission schemes, screen schemes, issue type schemes..etc... This leads to better continuity across the enterprise so everyone is not just doing their own thing and you have a more standardized setup.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Recommended Learning For You
Level up your skills with Atlassian learning
Learning Path
Jira Administrator
Configure Jira Software, Jira Core, or Jira Service Management, including global settings, permissions, and schemes.
Managing Jira Projects Cloud
Learn to create and configure company-managed projects in Jira Software and partner effectively with Jira Admins.
Learning Path
Become an effective Jira Software Project Admin
This learning path is designed for team leaders who configure Jira Software projects to match a team's processes.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.