If I have a sprint under planning and decide to add a new story directly to the sprint is does not work. The story is created but automatically moved to the backlog. Yes, I have double checked so that it really says 'New Story in "MVP Sprint 1"' and not "Backlog".
Yes, I do.
No message. The page just reloads and the story ends up in the backlog. I'm runinng the latest version of JIRA 7.4.3.
I'm using JIRA as a server install. I tried the same actions on JIRA Cloud and there it works as expected. So it would be really interesting if someone else is using the server install and can see if it worls for them. If so there must be a miss configuration somewhere.
I might point out that I'm using the built in Scrum Workflow.
Thanks for you response! I've added the screen shot which I hope you asked for. :) Took me a while to find. Also the permission sounds interesting but as always with JIRA where are those specifically found? If I look at Project permissions -> Issue permissions I can see that on Create Issue and Edit Issue it says "Application access - Any logged in user". Is that correct?
Yes, I looked at the permissions (se answer in last comment).
"Also the permission sounds interesting but as always with JIRA where are those specifically found? If I look at Project permissions -> Issue permissions I can see that on Create Issue and Edit Issue it says "Application access - Any logged in user". Is that correct?"
BTW How do I see the create transitions?
Ok, for the permissions you can find it in "Project settings - Permissions". Application accees - any logged in user means that you also have that permission. Is it the same for the "Schedule issue" permission?
To see the create transition you can select your workflow in edit mode (the diagram view), then click on the "Create" transition (should be the first arrow in your diagram) and then click on post-function.
It seems fine. Unfortunately I have no other idea of what your problem could be.
Next step is to check here if there is a similar open issue. Else you could contact Atlassian support to check that with them (unless anyone in the community has other idea on how to fix it?).
Will do! FYI I installed a brand new server with new JIRA Server installed. Imported my project into the new server and it worked.
So there is something fishy about our current JIRA installment.
I also do not want to backup and restore everything to the new seerver as then I probably restore the bug too.
Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...
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!
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