Creating access permissions on Goals

[Filipe Vítor]

Is the option to configure permissions to access specific goals in your roadmap for any time soon? We need to be able to configure who can access, view or edit each goal to be able to use the Goals feature. Currently we do not use Jira Goals because all goals are visible to everyone. 

This ability to manage permissions is critiocal to our adoption of the goals feature. Atlassian has mentioned for some time that this is in the roadmap, do you have an estimation on when it will be released? 

[Martin Runge]

Hi @Filipe Vítor

If you check the official Atlassian Cloud Roadmap (https://www.atlassian.com/roadmap/cloud), there is currently no estimated release date or active tracking item for introducing completely private or hidden goals.

The recently rolled out granular editor permissions mention in the last update a coming restricted goals feature for the Goals app, but for now, the available functions do not meet your requirements: https://community.atlassian.com/forums/Goals-and-Projects-articles/Now-available-Editor-permissions-in-Goals-and-Projects/ba-p/3224785

Since total visibility control is critical for your team, I would suggest a temp. workaround, creating a custom issue type called Goal within a standard Jira project. You can then apply a native Issue security scheme to that project to restrict both viewing and editing access to specific project roles or groups until the feature is officially added to the global roadmap.

[James Gamble]

Hola Filipe,

This looks like it’s in progress, but not fully available to everyone yet.

Atlassian now has documentation for goal permissions, but the page says the feature is currently in early access and available only to selected customers. It also says the feature is expected to roll out to all customers later this year: https://support.atlassian.com/platform-experiences/docs/set-up-permissions-for-goals-app/

There’s also a recent Community update saying editor permissions for Goals and Projects are available now, while restricted goals are still actively in development: https://community.atlassian.com/forums/Goals-and-Projects-articles/Now-available-Editor-permissions-in-Goals-and-Projects/ba-p/3224785

So today, you may be able to control who can edit goals, but full visibility control for restricted/private goals may depend on whether your site has the early access feature yet.

If goal visibility is critical before that rollout reaches your site, I’d use @Martin Runge workaround and track sensitive goals as a Jira issue type for now, then protect them with Jira issue security or project permissions. It’s not as clean as native Goals permissions, but it gives you actual access control until restricted goals are available in your tenant.

Thanks,

James