nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How does browse archive permission work?

Lara Lopez Garcia

Hello,

I have been testing the Jira Data Center archive feature. Neither the Global browse archive permission or the project archive permission seem to do anything.

Without configuring any of these permissions, users from a projects are still able to see the archived issues with a direct link.

What is the point of these permissions if users are able to check issues freely? Is there a functionality that I am missing? Is it linked with other permission? I understood that the browse archive would give admins the power to hide archived issues so that only users with the permissions can see them, but I have tested it and leaving both blank everyone can find the tickets with the direct link.

Best Regards

Accepted answers

Daniel Ebers

Hi @Lara Lopez Garcia

not being an expert on archiving at least I want to share that the direct opening of an issue via key seems to be intended behaviour:

Issues will be read-only and accessible only with a direct link

For the restore and archive permission question documentation says:

The Archive and Restore per project permissions allow you to archive and restore issues in a specific project.

For the browse issue archive it reveals:

In addition to archive and restore, there are the global Browse Archive and Browse Project Archive permissions. These permissions allow you to access the Archived issues pages and use the filters to find the issues you need - either all of them of those that belong to a specific project.

This all was taken from here:
https://confluence.atlassian.com/adminjiraserver/archiving-an-issue-968669980.html

When you say switching those permissions on/off does not do anything it might be the executing user is an administrator which type of account does have the permissions anyway.

If this all does not apply it would be hard to diagnose, then only the probability comes to my mind that the permission scheme is not the right one to look at.

Please do let us know if you have further questions, maybe the answer was not able to cover the question fully - then just leave feedback here.

Thanks in advance!

Regards,
Daniel

All comments

Kian Stack Mumo Systems

@Lara Lopez Garcia,

The point of the archive feature is to exclude the issues from the search index. By removing them from the search index, you can increase the performance of dashboards, search filters, and agile boards.

If you want to archive and hide them, you would need to update the permission scheme to remove the "Browse issues" permission from the project.

Lara Lopez Garcia

Hello Kian,

That´s not my question. I understand how browse issue works and what archiving does. But I cannot find any documentation on what the permissions ¨Browse issue archive¨ does, and what is the point of giving it to users.

Datacenter brings 3 new permissions, archive, restore and browse archive issues. Archive and restore work, without them, users cannot archive or restore, but it does not matter if I give my users the Browse archive issue permission they can do the same things. What I want to know it what is the difference of giving users this permissions.

Best Regards

Daniel Ebers

Hi @Lara Lopez Garcia

not being an expert on archiving at least I want to share that the direct opening of an issue via key seems to be intended behaviour:

Issues will be read-only and accessible only with a direct link

For the restore and archive permission question documentation says:

The Archive and Restore per project permissions allow you to archive and restore issues in a specific project.

For the browse issue archive it reveals:

In addition to archive and restore, there are the global Browse Archive and Browse Project Archive permissions. These permissions allow you to access the Archived issues pages and use the filters to find the issues you need - either all of them of those that belong to a specific project.

This all was taken from here:
https://confluence.atlassian.com/adminjiraserver/archiving-an-issue-968669980.html

Please do let us know if you have further questions, maybe the answer was not able to cover the question fully - then just leave feedback here.

Thanks in advance!

Regards,
Daniel

Lara Lopez Garcia

Hello Daniel,

The documentation lacks clarity and does not work as expected.

From my last tests I conclude:

The global permission: Browse Archive does nothing. I have the permission empty and users can still see the archived issues.

The Browse permission archive by project, stops users from finding the the project browse archive in the issue navigator. But they can still reach the issues if they have a direct link.

I have written directly to Atlassian support to see if they can explain it better.

Best Regards

Daniel Ebers

Contacting Atlassian support is generally a good idea when conversation in Community is stuck - just fine.
In case you have feedback from support I am sure Community members would be eager to learn what the result/outcome is.
That could help users with a similar question to learn how it works.

So - if you'd like to share the result I believe users would be very happy

Lara Lopez Garcia

Hello Daniel,

In case you are interested I was right the permissions where not working, Altassian resolved it for me as they are impacted by other permissions.

Granting Browse Project permission to 'Current Assignee', 'Reporter' or 'User Custom Field Value' allows all users to view Project information, including skip the browse archive permissions.

The bugs are these:

https://jira.atlassian.com/browse/JRASERVER-34389

https://jira.atlassian.com/browse/JRASERVER-37117

Best Regards

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Unanswered
Groups
Help

Find more posts tagged with

server

jira

jira-server

data-center