Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

Recognition

  • Give kudos
  • My kudos

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

When I create a sub-task from an Issue, the Create screen does not stay in that same sub-task.

In Jira Cloud, in a Classic Software Project, we have a list of subtasks to choose from.

When you select 'Create Sub-task', and choose the sub-task that you would like, the Create screen doesn't follow that sub-task and defaults to a different one on the list. The project uses several different issue types and corresponding sub-tasks and thus must use the same issue type scheme since they are all part of the same project. This issue type scheme has a list of different subtasks. How do I associate an issue type with one sub-task and then have that sub-task be the one that is already selected on its Create Screen?

 

Screen Shot 2020-01-14 at 10.16.46 AM.pngScreen Shot 2020-01-14 at 10.16.56 AM.pngScreen Shot 2020-01-14 at 10.17.19 AM.png

2 answers

1 accepted

1 vote
Answer accepted

To get the message you are seeing, you must have different fields and/or workflow between different types of issue.  When you're trying to swap between them, it is realising there is a difference and hence giving you the error.

> This issue type scheme has a list of different subtasks. How do I associate an issue type with one sub-task

Simply put, you don't.   All sub-task types are available to create from any issue type in the project, they're not dependent on each other.  You can do some stuff in the workflow that would block the selection of certain types (specifically, a validator on create that checks the pairing and rejects the attempt to create, but this is not a nice thing to do to your people as the failure will lose what they've entered)

Do you know if there is a feature request out to Atlassian for this functionality?

I have seen one, but it was closed "won't do" years ago.

0 votes

Hi @James Breunig 

May be it is worth checking the screen associated with that sub-task. Screens have 2 level of mappings - first with the Issue Type (including sub-tasks) and second with the operation (Create, Edit and View). This page has detailed information on this topic.

I hope it helps.

Ravi

You can also try disable the new issue view.

This is not dealing with a field. This is the Create Subtask button and the action that takes place after it is selected. The New Issue View is desirable for the rest of the layout and features, it's only this Create Sub-task feature that we are wondering why it is not functioning as intended.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Software

How to create Jira issus from Excel file?

When to use CSV importer When managing your processes in Jira, there are many occasions where you need to create a lot of tasks. Creating them one by one will cost you a lot of time and effort and i...

4,534 views 22 32
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you