nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Change "story" to "task"

Steve Kadish

Hello,

Is there any way to change the type of an issue from "story" to "task"? We had a bunch of projects moved from a project management system to Jira. Now we've got all sorts of "epics," "stories," "tasks," etc. Our team is not a software development team and most of these terms are completely meaningless for us. I honestly no idea why we are using Jira for managing IT projects that have nothing to do with software development.

Accepted answers

Bryan Trummer - ReleaseTEAM

Hello @Steve Kadish and welcome to the Atlassian Community.

You should be able to update a story issue to a task issue.

If you go to edit the ticket or click on the issue type on the ticket - it should allow you to change the issue type from "Story" to a " Task". However, if that doesn't allow it that is due to the issue types using two different workflows. You can still make the change but it is a little more involved.

Please reference this document that will describe how to achieve this.

https://support.atlassian.com/jira-service-management-cloud/docs/move-a-request-to-another-service-project/

Hopefully, this helps!

John Funk

Hi Steve,

If they share the same workflow, you can just update the issue type field to Task.

If they use different workflows, then you have to do a Move on each card.

All comments

Bryan Trummer - ReleaseTEAM

Hello @Steve Kadish and welcome to the Atlassian Community.

You should be able to update a story issue to a task issue.

Please reference this document that will describe how to achieve this.

https://support.atlassian.com/jira-service-management-cloud/docs/move-a-request-to-another-service-project/

Hopefully, this helps!

John Funk

Hi Steve,

If they share the same workflow, you can just update the issue type field to Task.

If they use different workflows, then you have to do a Move on each card.

Steve Kadish

Hi John and Bryan,

Thanks, but what is a "ticket?" What is a "card" The article shows how to move something to a different project, but I just want to change it. Can you give me the steps for clicking on an issue called a "story" and changing it to an issue called a "task?"

The way this is set up is that there is a huge project called "IT Operations." It contains "epics" for pretty much every project we've ever started or discussed. Each of these "epics" is linked to a bunch of "stories" or "tasks" or "initiatives" that can be anything from a configuration step to a research idea.

In my mind, an "issue" is something that needs to be resolved. This is one of the reasons I'm having such a problem with this whole setup.

Steve Kadish

Hi,

Thanks, I figured out that you can use the Move function to change the issue type without changing the project. It says that it will break the link to the "epic" but that doesn't seem to be the case. It's time consuming to do this for each "story" (I still don't understand what a story is) but it's what I'll do for now.

John Funk

Sorry - a card, a ticket and an issue are all the same thing. People just use different terminology. To change it, you have to actually do a move if the issue types use different workflows.

So, start by clicking on the issue type of the issue and see if it will let you change it directly to the issue type you want. If not, then you need to click the 3 dots menu on the right and select Move. On the following screen, change the issue type to the one you want to move to.