This just started occuring in a Support Project we have had set up for a while. There are no notificaitons that go out and when I do go into the issue I can see the issue but only allowed to assign to myself.
That usually happens when you've given yourself "create" rights but not "browse" in the project.
However, the fact you can then see it later implies there is something odd going on.
First, can you tell us where you are doing the "create" from? Plain Jira? Service Desk? An Agile board?
Second, could you tell us what you have listed in the permissions for "create issue" and "browse project"?
Thing is, I'm getting increasingly convinced you're using Jira Agile, not plain Jira. Everything you're seeing is consistent with being in Agile, clicking "create", going through the creation process, and then creating an issue which does not match the filter you've got on that board. Not the "quick filter", but the actual board filter
If, for example, I'm on a board that has a filter of "Project = Who and component = Dalek" , I see all the Dalek related issues. I click create and create a new issue there, and put down component of Cyberman, instead of Dalek, then when I commit it, I get exactly the message you see. The issue can be seen in Jira, it can be searched, it works fine, but because it's not included in the board filter, it throws exactly "Jira issue is created but not currently visible"
The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...
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