You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Recently we had to cut costs and during this we also cut number of Jira licenses and therefore not everyone at the company have Jira accounts anymore. However I have two software projects that I need everyone at the company to be able to create issues in. Is this possible somehow?
At the moment when they try to open up a link to the create form (link directly to the create screen/fields from our intranet) they get a message saying "You are not logged in, and do not have the permission required to create an issue in this project as a guest"
Is it possible to set permission in the project for guests to be able to create issues? I have looked but can't find this.
I understand that the best thing would probably be to convert the project in to a service desk project and have them create issues via the portal but I don't really have the time to start that type of project now so I am trying to find a quicker solution.
In order to create issues in a JSW project you have to have a license. Without a license you can't do anything. You could however work with anonymous access https://support.atlassian.com/jira-cloud-administration/docs/allow-anonymous-access-to-projects/
Oki thank you for your answer @Alex Koxaras _Relational_ . I will look in to the "Public" permission to see if that could be an alternative for now.
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If the anonymous access will work for you, kindly come back an mark this answer as accepted, in order to help other with similar questions. Thank you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just an idea:
If it's possible for you to set up a JSM project, then you could create a form for issues submission, tie an automation to the creation of such tickets and have the automation create the actual JSW issues in their respective projects.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ah thanks! Hmmm, that might be a good idea. I would need to look into how to create that automation but I can definitely set up a JSM project. Do you think it is possible to also have the reporter follow the status of the issue via the JSM project in the service portal if the issue is handled in the JSW project? Maybe that would require an additional type of automation?
Also not sure yet how much work it is to convert a JSW project to a JSM project or if that is even possible. I will investigate this further before making any more advance work arounds I think :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You might have to set up several automations, indeed. But that's what Automation is for, right. So yes, you should be able to allow the reporter to keep track of progress via the "automated" JSM issue. See https://support.atlassian.com/jira-service-management-cloud/docs/edit-linked-issue-automated-rules/
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.