Unable to move issues across projects because "current project" is empty.

When I try to move an issue from "Project-A" to "Project-B", I am not able to because when I initiate the move in the "Move Issue" interface, I do not see the "Current Project" set to anything.  I was expecting it to see "Project-A" set there.

How do I go about fixing how to set the "Current Project" field correctly when creating an issue?

Thanks!

1 answer

1 accepted

0 vote

What's the "current project" field?  There's no such thing in JIRA natively, so is it a custom field? 

If you really do mean "current project" as in "what prject the issue is in", then you don't need it on screen because the issue already is in that project, and the move process will ask you for the target project.

I inherited the JIRA setup, but I think it is a custom field when I looked at the following article:

https://confluence.atlassian.com/jira/moving-an-issue-185729549.html

The graphic on step 3 of the above article shows a "Current Project" field set. The move does ask me for a Target Project that I can pick, but when I pick the "New Issue Type", it always complains that the "The issue type selected is invalid". I know that the "Target project" and the "New Issue Type" are valid selections.  The only difference I saw from the above article is the missing "Current Project" field, so I assumed that the "Move Issue" operation probably does not have enough context to complete the operations.

Thanks for helping me out!  

That's the target selection screen, it's showing you the current project and let you select a new one.  There's nothing missing there.

Try a simple experiment - select a target project first, then an issue type second.  Check that fails.  If it does, then try "create issue" and select the project and issue type - does that let you create a new issue with the new values?

 

Thanks, Nic.  It's actually the target selection panel where I am having the problem.

When I try to move an issue to a different project  (selecting target project first and them issue type) – I get the following failure message (note the empty current project):

Screen Shot 2016-04-22 at 4.43.00 PM.png

And, yes, if I independently try to create a new issue with the "target project" and "target issue type", it works fine.

Maybe the empty field is fine, and I need to enable something else allowing the "Move".

On the "empty project" - that doesn't really matter, as it doesn't get used.  Have a look at the OPS project though - what is displayed as the name?

On the red box - what happens if you click on the drop-down?

Yes, the OPS project is fine.  I have enabled create and move permissions on both the current and new projects...the drop-down does show me valid options for each of the "new project" if I try to change, but when I click on next, the only thing that happens is the message saying "The issue type selected is invalid."  I wish I could show it to you over a screen share! Thanks, Nic!

Ok, but what is displayed as the OPS project name?

The next step is logs I'm afraid.  Go to what you're doing already and trigger the error again, while watching what the log says.  That should tell you more about what is going wrong.

The OPS project name is correctly displayed.  The bulk edit interface for moving issues across projects works...just when we individually try to move issues across that our setup acts up.

Thanks for asking for the logs, here's what the they say when I hit the "next" button after setting up a New Project and New Issue on the move interface:

127.0.0.1 1392x1269747x1 psingh [25/Apr/2016:23:12:27 +0000] "POST /secure/MoveIssue.jspa HTTP/1.0" 200 50851 112 "<server>/secure/MoveIssue.jspa" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.86 Safari/537.36" "g6dk6b"

127.0.0.1 1392x1269748x1 psingh [25/Apr/2016:23:12:27 +0000] "GET /rest/menu/latest/appswitcher?_=1461625947430 HTTP/1.0" 200 625 5 "<server>/secure/MoveIssue.jspa" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.86 Safari/537.36" "g6dk6b"

127.0.0.1 1392x1269749x1 psingh [25/Apr/2016:23:12:27 +0000] "GET /rest/hipchat/integrations/1.0/configuration/status?_=1461625947507 HTTP/1.0" 200 77 5 "<server>/secure/MoveIssue.jspa" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.86 Safari/537.36" "g6dk6b"

Ok, that's good - the project field is healthy, and there's no errors showing on the front end.

The next thing to look at is the application log - it's usually <JIRA home>/logs/atlassian-jira.log

The only thing I see in the <JIRA home>/logs is a daily log file called access_log.<date>, e.g., access_log.2016-04-26. The output that I sent earlier was from that file only.  The other file I see in my <JIRA home>/logs/ is the catalina.out file, but that's for Tomcat,  I guess.

Here's log contents to show another example of an unsuccessful attempt to move:

127.0.0.1 130x1271280x1 psingh [26/Apr/2016:02:10:31 +0000] "GET /browse/OPS-92 HTTP/1.0" 200 86313 143 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.86 Safari/537.36" "1rbmyy"

127.0.0.1 130x1271281x1 psingh [26/Apr/2016:02:10:31 +0000] "GET /rest/menu/latest/appswitcher?_=1461636631456 HTTP/1.0" 200 625 5 "<server>/browse/OPS-92" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.86 Safari/537.36" "1rbmyy"

127.0.0.1 130x1271282x1 psingh [26/Apr/2016:02:10:31 +0000] "GET /rest/bamboo/latest/deploy/OPS/OPS-92?_=1461636631501 HTTP/1.0" 200 2 4 "<server>/browse/OPS-92" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.86 Safari/537.36" "1rbmyy"

127.0.0.1 130x1271283x1 psingh [26/Apr/2016:02:10:31 +0000] "GET /rest/hipchat/integrations/1.0/issuepanel/data/OPS-92?_=1461636631618 HTTP/1.0" 200 237 6 "<server>/browse/OPS-92" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.86 Safari/537.36" "1rbmyy"

127.0.0.1 130x1271284x1 psingh [26/Apr/2016:02:10:31 +0000] "GET /rest/api/2/filter/favourite?expand=subscriptions[-5:]&_=1461636631664 HTTP/1.0" 200 2 5 "<server>/browse/OPS-92" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.86 Safari/537.36" "1rbmyy"

127.0.0.1 130x1271286x2 psingh [26/Apr/2016:02:10:31 +0000] "GET /rest/hipchat/integrations/1.0/configuration/status?_=1461636631770 HTTP/1.0" 200 77 7 "<server>/browse/OPS-92" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.86 Safari/537.36" "1rbmyy"

127.0.0.1 130x1271285x1 psingh [26/Apr/2016:02:10:31 +0000] "GET /secure/AjaxIssueEditAction!default.jspa?decorator=none&issueId=12475&_=1461636631746 HTTP/1.0" 200 26371 35 "<server>/browse/OPS-92" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.86 Safari/537.36" "1rbmyy"

127.0.0.1 130x1271287x1 psingh [26/Apr/2016:02:10:31 +0000] "GET /rest/api/2/mypreferences?key=hipchat.inapp.links.first.clicked&_=1461636631835 HTTP/1.0" 404 84 5 "<server>/browse/OPS-92" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.86 Safari/537.36" "1rbmyy"

127.0.0.1 130x1271288x1 psingh [26/Apr/2016:02:10:31 +0000] "POST /rest/webResources/1.0/resources HTTP/1.0" 200 953 12 "<server>/browse/OPS-92" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.86 Safari/537.36" "1rbmyy"

127.0.0.1 130x1271289x1 psingh [26/Apr/2016:02:10:32 +0000] "POST /rest/analytics/1.0/publish/bulk HTTP/1.0" 200 - 5 "<server>/browse/OPS-92" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.86 Safari/537.36" "1rbmyy"

127.0.0.1 130x1271290x1 psingh [26/Apr/2016:02:10:34 +0000] "GET /secure/MoveIssue!default.jspa?id=12475 HTTP/1.0" 200 50756 59 "<server>/browse/OPS-92" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.86 Safari/537.36" "1rbmyy"

127.0.0.1 130x1271291x1 psingh [26/Apr/2016:02:10:35 +0000] "GET /rest/menu/latest/appswitcher?_=1461636635115 HTTP/1.0" 200 625 5 "<server>/secure/MoveIssue!default.jspa?id=12475" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.86 Safari/537.36" "1rbmyy"

127.0.0.1 130x1271292x1 psingh [26/Apr/2016:02:10:35 +0000] "GET /rest/hipchat/integrations/1.0/configuration/status?_=1461636635183 HTTP/1.0" 200 77 5 "<server>/secure/MoveIssue!default.jspa?id=12475" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.86 Safari/537.36" "1rbmyy"

That is NOT the <JIRA home> directory.  You've looked in the <JIRA install> directory.

Please look in JIRA home, where all the data is.

Here's what I see in that log (when I just tried to move) – it seems that the original issue (maybe because the current project name is blank) is not found and is null.

2016-04-26 14:55:57,740 http-nio-8085-exec-24 ERROR psingh 895x1276404x1 gkwvhb 108.28.102.80,127.0.0.1 /secure/MoveIssue.jspa [c.a.j.w.action.issue.MoveIssue] Exception: com.atlassian.jira.exception.IssueNotFoundException: Issue with id 'null' or key 'null' could not be found in the system

com.atlassian.jira.exception.IssueNotFoundException: Issue with id 'null' or key 'null' could not be found in the system

        at com.atlassian.jira.web.action.issue.AbstractIssueSelectAction.assertIssueIsValid(AbstractIssueSelectAction.java:489)

        at com.atlassian.jira.web.action.issue.AbstractIssueSelectAction.getIssueObject(AbstractIssueSelectAction.java:157)

        at com.atlassian.jira.web.action.issue.MoveIssue.doValidation(MoveIssue.java:152)

        at webwork.action.ActionSupport.validate(ActionSupport.java:391)

        at webwork.action.ActionSupport.execute(ActionSupport.java:162)

        at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:63)

        ... 7 filtered

        at javax.servlet.http.HttpServlet.service(HttpServlet.java:725)

        ... 50 filtered

        at com.atlassian.greenhopper.jira.filters.ClassicBoardRouter.doFilter(ClassicBoardRouter.java:59)

        ... 151 filtered

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

        at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)

        at java.lang.Thread.run(Thread.java:745)

 

Ok, that's one of several things, possibly.

Could you look at the "create" transition on the target project/issuetype?  Are there any validators or post-functions on it?  (JIRA will have 3 post-functions automatically)

Are both your source and target issue types included in the default issue type scheme?

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published Thursday in Jira

5 ways you can make the most of Jira Software and Bitbucket Cloud

As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...

82 views 0 5
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you