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
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
Can i give an user view in a project only to his created tickets?
I need to configure this to some users permissions to a Jira Software Project. I want to give those users view just to the ticket that they create.
Is that possible?
Hi @Cesar Bastos ,
you need to setup project permission scheme so that just reporter has "Browse project" permission. In that way, just who creates tickets (should be the default reporter) can view his own tickets.
Hope this helps,
To supplement what others have suggested, if you only want the reporter to access/view to tickets that are created by himself/herself (and not other tickets), then you will need to implement issue security configuration against your project(s) in question.
Here is a link for your reference - https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-security-schemes/
This implementation will lockdown issue visibility as per your configuration setup + tagging the issues with the appropriate security level attribute. If a user is not call out (i.e. reporter) in the issue security, then he/she will not be able to discover the issue/access the issue. This will automatically be in place against any board/view/direct issue URL.
NOTE - Once the issue security configuration is setup against a project, it is setup from that point going forward. All issues existed prior to the implementation will need to be updated via bulk change operation to apply the appropriate security level manually.
Hope this helps.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Infrastructure Applications Team
Yes in the security level configuration. You should need to ensure that members of project Administrators and Developers roles are also called out in the security level.
You can use Issue Security Scheme for this. You can use the Issue Security Scheme level on the post-functions to update the security level on certain statuses if you want. More customization can be done using Automation for Jira.
Hi everyone! I actually have a project where I sucessfully implemented this solution but because we're grating browsing rights the "reporter", the project becomes automatically discoverable, i.e., although you cannot see anything in it, the project itself shows as a project.
The reason behind this statement is just because I had to set another project that will be shared with an external person and this external person will be able to see it, whereas the remaining projects stay "hidden".
Any suggestion to circumvent this visibility issue?
I use and promote the use of this filter and board. This is the first place I go each morning. It displays all issues that I have reported or assigned to across all projects. I can then use quick filters to see what I want to see. I share this filter with the entire company as it works on the current user.
the filter: assignee = currentUser() OR reporter = currentUser() ORDER BY createdDate DESC
The board is set up with these quick filters.
|Urgent/High||priority in (High,URGENT)|
|assigned to me||assignee = currentUser()|
|reported by me||reporter = currentUser()|
|In Open Sprints||Sprint in openSprints()|
|Open Issues||resolution is EMPTY|
|Show Story/Task/Subtask Only||issuetype in (Story, Task, Sub-task)|
|Hide Sub-Tasks||issuetype != Sub-task|
|Not Updated Today||updatedDate >= -1|
|Not updated in last 14 days||updatedDate >= -14|
|Created today||created >= startOfDay()|
|Show Epics Only||issuetype = Epic|