Question about the new Atlassian Jira surface: Creation of templates and issues

[Witt_ Laura Kristin _MRB-R_]

Our team has been using the new Jira Board for a few weeks now and we have a few questions about the new features.

Firstly, we haven't yet figured out how to place newly create (or cloned) tasks directly into the current sprint. Until now, these tasks always end up at the bottom of the backlog and then have to be manually moved to the top. Is there a faster solution for this?

And is it possible to create templates in such a way that they are automatically placed in
the current sprint, i.e., are “carried over” to new current sprints?

Also, we were trying to change the container of each issue in the editing mode, since there was a drop down menu in the old surface that we can't find in the new version.

Lastly, we would love to pin a template issue at the left side menu, which we can use as a clone and which also contains the drop down menu/container options.

Can you help us here, or do you have a tip for us?

[Luka Hummel - codefortynine]

Hi @Witt_ Laura Kristin _MRB-R_ and welcome to the community!

If you are willing to use an Atlassian Marketplace app, our app Deep Clone for Jira can help you with your questions:

1. Put newly created/cloned issues straight into the current sprint

   • Deep Clone dialog → Sprint: When cloning, tick Sprint to carry over the sprint. Only open sprints (active or future) can be cloned.
   • Edit fields: Click Open Field Editor and set Sprint explicitly to your active sprint during the clone. This avoids cloned items landing at the bottom of the backlog.
   • Tip: If you clone into another project, Deep Clone can Create a sprint with the same name when needed, so sprint context stays intact.
     

2. “Templates” that always land in the current sprint (carry-over)

   • Presets: Create a Deep Clone Preset with your template issue(s) and the sprint/field edits you want. Team members run it from the Actions menu (•••) in one click.

[Marc - Devoteam]

Hi @Witt_ Laura Kristin _MRB-R_ 

Welcome to the community.

1. When creating a new work item, to be directly in the active sprint, the Sprint Field should be filled on creation with the correct sprint name.
   
   So is the Sprint field on the creation screen when creating a new work item.
   
   NOTE: this isn't a best practice, because probably not every new created work item needs to be assigned to the active sprint.
2. You could create an automation rule for this, based on work item created trigger, set conditions based on your need and then use an edit action.
   
   See: https://support.atlassian.com/jira-software-cloud/docs/add-issues-to-an-active-sprint/
   
   Same NOTE: this isn't a best practice, because probably not every new created work item needs to be assigned to the active sprint.

Can you clarify a bot more on the other topics, what are you meaning with container and template issue

Also, we were trying to change the container of each issue in the editing mode, since there was a drop down menu in the old surface that we can't find in the new version.

Lastly, we would love to pin a template issue at the left side menu, which we can use as a clone and which also contains the drop down menu/container options.

[Witt_ Laura Kristin _MRB-R_]

Hi @Marc - Devoteam thank you for your quick reply!

We work with different general categories for issues, which we sometimes need to change depending on the issue that we create. It's the function with the purple lightning icon. In the old surface, there used to be a drop down menu to change the category.

About the template issue: in the old version we had linked the template issue in the menu on the left side, so we could easily access it and clone it to create new issues. However, we couldn't find this function in the new version. We use clones, because they contain all relevant settings (like categories), which makes it a lot easier to create new issues.

Thank you so much for your support! 

[Marc - Devoteam]

HI @Witt_ Laura Kristin _MRB-R_ 

Do you mean an work item of type Epic?

You need to use the parent field for this.

Can you provide screenshots to even clarify this a bit more?

This template option you are referring to is not an ootb function, is this from a 3rd party integration?

Then look for this under the apps option in the left hand menu

[Witt_ Laura Kristin _MRB-R_]

Hi @Marc - Devoteam 
Yes, we mean the different types of Epics. We would like to have all the items of the Epic in a drop down menu within an issue (so we can change items when editing an issue) --> See the pitcure below

We mean this:

What do you mean by parent field? Do we have to create a template issue for each epic item?

Regarding the template, we just mean the regular templates in Jira. In the old version, we were able to link issues in the left side of the menu. Does that function still exist? Otherwise we need to scroll down to the very bottom of our current sprint (which includes the tasks of all team members) to find the template. Having it linked in the menu on the left makes it easier to edit it. All team members are using this template, so it would be a really easy way to create tasks (issues) faster.

Thank you so much!

[Marc - Devoteam]

Hi @Witt_ Laura Kristin _MRB-R_ 

I don't know what you mean, I'm not german.

To link Epic issues with their child's you use the field "Parent" in the child issue to link it.

But I think übergeordnet is the field "Parent".

This field needs to be on the screen.