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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,461,714
Community Members
 
Community Events
176
Community Groups

Move Issue from one project to another project

Hi,

Who is responsible for moving the issue from PROJGEN12 board to SV77G12 board.

PROJGEN12 --> 77 GHz Gen 1.2 Project (PROJGEN12)

SV77G12 --> 77GHz Gen 1.2 V&V (SV77G12)

2 comments

Hi @Viji and welcome to the community!

I guess you're talking about something that happened in your company's Jira instance? Let me try to help out.

A board is a collection of issues returned by the board filter. So the issue hasn't moved between boards. It may just be included by the board filter now. 

But did the issue move from one project to a different project? Take a look at the issue's activity/history tab and you should be able to find out who made what changes to the issue. :)

Best, Max

Hi Max,

Thank you for your reply.

In my case, we as a verification team had created issue in SV77G12 board. This issue was related to requirement, hence the ticket was moved to PROJGEN12 board. PROJGEN12 board deals with requirement issue. Now the requirement issue has been resolved. The requirement engineer has provided the comments in the PROJGEN12 board. Now who is responsible to move the ticket back from PROJGEN12 to SV77G12 board?

Hi @Viji ,

Board Administrator (who created the board) can do this. if you want to move the issues from one project board to another project board then you can go to  Board Setting-> Edit Filter and set the filter accordingly.

Hi Monika,

Thank you for your reply.

In my case, we as a verification team had created issue in SV77G12 board. This issue was related to requirement, hence the ticket was moved to PROJGEN12 board. PROJGEN12 board deals with requirement issue. Now the requirement issue has been resolved. The requirement engineer has provided the comments in the PROJGEN12 board. Now who is responsible to move the ticket back from PROJGEN12 to SV77G12 board?

Hi @Viji ,

PROJGEN12 team can move the issue back to SV77G12 board. But they should know this they will move the issue if not you can help them.

Hi @Monika Rani ,

Is there any reference document which talks about responsible person to move the ticket from PROJGEN12 to SV77G12 board.

Hi @Viji ,

There is no word "responsible' here if someone has permission to move the issues they can perform this.

Related to the permission Please have a look this:  https://confluence.atlassian.com/jirasoftwarecloud/permissions-overview-764478244.html

and https://confluence.atlassian.com/adminjiracloud/managing-project-permissions-776636362.html

If you have Admin access you can play with these permissions.

If you found this helpful please accept the answer.

Thanks,

Monika

Hi @Monika Rani ,

Thank you for your inputs.

Comment

Log in or Sign up to comment