We have a user that is unable to attach a file to an issue. It says that the project cannot be found.
Error.jpg
However, according to the Permission Helper, the user does have the necessary permissions.
2016-03-24_14-36-47.jpg
That said, the user should only have permissions to Create Issues, Create Attachments, and Move Issues for the project. They can create the issue with attachments in another project with more permissions and then move it into this project while maintaining the attachments.
Hi Brad,
looks like this issue have happened before:
https://jira.atlassian.com/browse/JRA-31669
It is still not resolved, I suggest you write in the existing bug and escalate.
There is a KB for a similar issue although not related to attachment and the solution seems to be to edit project key - see more details here:
https://confluence.atlassian.com/jirakb/no-project-could-be-found-with-id-xxxxx-420971893.html
Update the thread if you have success.
Thanks,
Peter T
Could you give us the text in red? The screenshots are too low-res to make it out.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It reads:
Cannot attach file After_Allowing_Insecure_JavaScript.jpg: No project could be found with id '10700'.
Also, I can attach files without issues but I have full permissions to the entire project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hmm, I've seen that before, can you tell us what the project key is?
Also, can anyone attach it, or is it blocked to everyone?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Some people can attach, but some cannot. Those that cannot have the lesser permissions (Create Issues, Create Attachments, Move Issues) on the project. The project key is 'PROD'.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ah, crossed comments, sorry!
Ok, the key of PROD rules out what I'd remembered (a numeric project key causes this problem), so a few more debugging questions
(Actually, the answer to the first one would give me a bit more to look at faster than you trying the other two)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Any suggestions? We don't want them to be able to see other issues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ah, no, that makes sense, you do need browse to be able to see the issue to which you want to attach it, so you must grant browse project to them.
To hide other issues, you usually use the issue security schemes (The reason I said "usually" is that if you want "reporter can only see their own reported issues", you can enable "reporter browse" to do that instead, it's far better than issue security)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.