I'm getting this error message when creating a cetain issue type called "Todo".
I've analyzed the issue type to find any difference to other issue types that are working as they should, but at this point im clueless of whats wrong.
Sub-tasks are defined in an own issue type, the sub-task issue type are on -1 in the issue hierarchy. "Sub-task" issue type are configured as an subtask type of issue in the config.
Todo issue are on level 0.
Both issue types are configured in the issue type scheme used in the project.
Any ideas of where to look next??
Hi Lars,
A couple of questions - is there is a post function in the workflow that fires during the create to create sub-tasks for this workflow?
Second, why are you creating an issue type called To Do? That's a status, not an issue type.
Third, what type of project is this? Software? Business? Is it Company-managed or Team-managed?
Hi John, thank you for the tip.
Actually I hadn't checked the workflow scheme. There was an error there, the To Do issue type was assigned to the subtask workflow. Reassigned it and problem solved.
The issue is called "To Do" because my boss wanted me to name it like that...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yeah, this is one of the times you should stand up and tell your boss they are wrong.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Welcome to the Atlassian Community!
I strongly recommend getting rid of your "to do" type, it's the wrong name for an issue type. You're putting people in a place where they are seeing "not to-do called to-do" in their reporting. Completed / ended / finished / cancelled issues should never be shown as "to do", because they are not. Choose a word like "task" instead.
Anyway, the question. You have a validator or Behaviour on this issue type that is telling you that you're not allowed to create sub-tasks on the issue type.
Jira does not have any functionality that blocks sub-task creation on specific issue types. If there is one or more sub-task types in the issue type scheme, then that type can be created below any base-level issue type.
So someone has coded something to give you this message. If it's a Behaviour, it's only a warning, you can ignore it. If it is a validator, then you're going to need to either get it fixed (i.e. removed, because it's a bad pattern, blocking your work), or change what your are entering into the issue such that you do not trigger it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.