Can we move issues from one project to another in Jira

The Move Issue wizard allows you to specify another project in your Jira instance to move your selected issue to. As there may be significant differences in the configuration of your original project and target project, the Move Issue wizard allows you to change certain attributes of the issue.

How do I move an issue from one board to another in Jira?

@Roja Gurram You can click on the dot menu in the top right of the ticket and select “Move”. Then move it to whatever board you want.

Can a Jira issue be in multiple projects?

Unfortunately you can’t have the same issue in multiple projects, you will need to have individual issues in each project. … so, in that Board you will allocate issues from Service Desk and from the Jira Project.

Can you link issues between projects in Jira?

Open the issue you wish to link to another issue in the same Jira site. Select More > Link to display the Link dialog box. Ensure that the Jira Issue item is selected at the left of the dialog box and then choose the type of link to be created from the This issue drop-down list.

How do I move a story from one board to another?

Move a story to anywhere from anywhere You can move any story to anywhere if you have a write access right on both the target and the source workspace. Open the [⋮] menu of a story card on the board or the backlog and select Move to > Another project/team.

How do I link two issues in Jira?

Open the issue that you want to link to.
Select more (•••) > Link > Jira Issue.
Choose the relevant Jira site and the type of issue link.
Enter the issue key or search for the issues you want to link.

How do I move an epic from one board to another?

From your Epics panel (click Epics in the sidebar), expand the Epic you wish to move and select Add/View stories to open a new panel with its associated stories.
Click the Panel Actions menu icon at the top right of the panel and choose Select All.

How do I link two Jira projects?

Choose Administration ( ) > Projects. Select the project that contains the fields you need to configure. On the Jira project configuration page, go to the Fields section. On each field where you will create links, click the Renders link.

How do I combine issues in Jira?

you can’t merge issues. I would link them as duplicates and close one of them. You can add the author of the first one as watcher for the second one, if you want.

How do I manage multiple projects in jira?

If you are using classic projects, then you can create a board that have multiple projects by creating a board for one project then editing the JQL that defines the board filter to add other projects.

Article first time published on

How do I bulk move tickets in Jira?

Perform a search with the required filters to produce a list of issues.
Select Tools > Bulk Change.
Select the issues you’d like to perform the bulk operation on, and select Next. …
Select Move Issues, and select Next.

How do I copy a story in Jira?

To clone an issue, just select clone from the Actions menu. Jira automatically adds “CLONE” to the beginning of the summary of the new issue, and you can activate the option to clone attachments if you want.

How do I move a Jira story back to backlog?

If you want to move the issue to the backlog you can : drag the issue from the sprint to the backlog in the backlog tab of the board. right click on the issue and select move to top/bottom of backlog (again in the backlog tab of the board)

Can I move epics between projects Jira?

EPIC type should behave the same way when you “move” issues between projects. You simply use the Move operation. However, moving an epic does not move the underlying issues so they must be moved separately. The move operation is found under the ellipses when viewing the issue detail view.

How do I move a project from one project to another?

Click and drag an entire Section into the side-bar and drop it into a different Project (have a “Move or Copy” pop-up)
Have a menu pop-up on a Section that has an option to Move or Copy to another Project.

How do you move problems from one project to another?

View the issue that you wish to move.
Select More > Move.
The first page of the Move Issue wizard is displayed. Complete the steps required.
The confirmation page will display with all of your changes. …
Your issue will be moved to the target project and displayed on screen.

What is cloning in Jira?

Cloning enables you to duplicate an issue within the same project, copying over most information from an issue like the Summary and Description fields and more. Cloned issues exist as a separate entity to the original issue.

How do I share an issue in Jira?

Open the issue view of the request.
Click the share icon ( ).
Enter who you want to share the issue with and a message to send them.
Click Send.

Is related to in Jira?

You can name both roles equally (“is related to” — “is related to”), and this will work to some extent. You can expect “is related to” appear twice where you select a link type, for example. In your JIRA configration, this probably lead administrators to define the roles for the “related” link type differently.

Can we merge two tickets in Jira?

You can’t merge tickets. However you can link both issues and mark one as a duplicate of the other. Thanks to automation rules, you can certainly update both tickets in the same time.

How do I group tickets in Jira?

Find the the dropdown menu labeled Group by, then select how you want to group your issues. If you group by component or label, select + Create group. Enter a name, and then start typing to find the components or labels to add to the group.

How do I merge cards in Jira?

Right now, there isn’t a way to merge two cards. Instead, we’d suggest adding a link for the secondary card onto the original, and then archive the secondary card. That way, you can access that information quickly without having an extra card visible on the board.

What is Exalate in Jira?

Exalate provides a flexible synchronization engine such that issues are automatically and securely synced – between multiple Jira’s – wherever hosted. Benefit from a unified view and integrated workflow!

What are cross-project setups in Jira?

Cross-project releases are used to manage joint releases, dates and milestones across multiple individual projects. When you create a cross-project release and commit it to Jira, the release will be transformed into a regular release in each of the Jira projects that are part of the cross-project release.

How do you manage multiple projects?

Plan before starting anything. …
Use every tool at your disposal. …
Prioritize tasks. …
Adjust your plan through regular reviews. …
Know when to delegate. …
Stay focused. …
Communicate with team members.

How do I create a cross-project release in Jira?

Go to your plan > Releases > + Create release. Select the release name, choose Cross-project release. Click Add and select the projects that will be sharing this release. Select the dates.

Can a Jira project have multiple workflows?

Welcome to the Atlassian Community. Your project can have multiple workflows, but not multiple workflow schemes. … So you would have to create new issue types to place in the same workflow scheme is you add new workflows.

Can I create multiple boards for one project in Jira?

You can just create 3 separate boards based on the necessary JQL filters. If you want to see them on one board, then use swimlanes or quick filters to separate them. You can split them by Component or a custom field.

What is the difference between a board and a project in Jira?

Project is a collection of issues where we split requirements, tasks, and release plans within a project. Board is an intuitive representation of a project, which can include one or more projects, depending on the filter configuration of board, including kanban board and Scrum board modes.

How do I track multiple projects in Jira?

To track requirements across multiple Jira projects, you can create an issue in each project – and then relate them together. You can have one requirement issue being “owned” by a specific project and then close all the related issues once you test them or decide to apply changes.