📣 Planned maintenance on Sunday, January 18, 2026

[#1]

Hello JPD community,

We are scheduling another short maintenance window to make your experience smoother and more reliable.

The maintenance will take place on Sunday, January 18th, 2026 between 11 AM UTC and 12PM pm UTC. This maintenance will impact edit actions in Jira Product Discovery spaces. There will be no impact to view or browse any parts of the site during the maintenance window.

During this maintenance window, any attempts for edit operations will return an error.
If end users receive an error when editing during this time, they should refresh the browser and re‑submit the change once the maintenance window has finished.

Note: During the scheduled maintenance, customers are not entitled to SLA credit compensation as outlined in our legal agreement.

Thank you for your patience and understanding as we work to improve performance for all our customers!

Cheers,

Rishabh Jha

Sr. Software Engineer @ Jira Product Discovery 

[Mirek]

Thank you @Rishabh Jha for detailed information about upcoming maintenance. That is always helpful when people raise questions or problems at that time. 

[Elie Théocari]

Hello @Rishabh Jha , is it possible that this maintenance caused a regression on existing permissions?

We have a few users with Contributor permissions, who cannot access JPD anymore, since this morning (Jan 19). On the lines corresponding to each of them in /settings/access, we now have the message "The user needs a license to have creator access to this space. Contact your site admin to request a license."

I'm not trying to give them Creator permissions, so the message seems a bit off.

Also, when clicking on the "Manage roles" button, I notice that a permission "Copy this space - Use this space as a template when creating a new space." is checked for the Contributor role. But it does not have the FREE label, so it looks like a potential reason why the Contributor role is not available anymore to people without a JPD license.

For now, as a workaround, I granted these people with an Observer role instead of Contributor. But of course, we need them to be able to contribute, so I hope that you can enlighten me soon.

Thank you in advance for your help on this.

[Rishabh Jha]

@Elie Théocari - The migration was a different Database. It did not touch any of the permissions flow. So the changes could not directly contribute to any of the permission issues. 

[Elie Théocari]

Thank you @Rishabh Jha for your answer. I still cannot understand how come we have this issue now, which we did not have until this morning, and we did not change anything related to permissions since then. I would have happily tried to remove this non-free permission from the Contributor role as a test,  to see if it works better with free permissions only. But this is a standard role, so I cannot.

Do you please have an idea of where I could look in order to make some progress?

[Elie Théocari]

Hello @Rishabh Jha , and anyone who would have the same issue,

I used this workaround to fix my issue:

• In the space settings in JPD, Access, I duplicated the native Contributor role into a new "Contributor (custom)" role.
• I kept all the same permissions as for Contributor, except the "Copy this space" one.
• Now, the "Contributor (custom)" role appears as FREE, whereas the native "Contributor" role does not.
• And I don't have the warning message anymore.

This is how I am restoring access to JPD to my contributors, given that we changed no configuration on our side between Jan 16 and Jan 19.

Edit: I don't think that my contributors need a permission to copy a JPD space to a new one. If we are ever to do this, they will ask an administrator.

Have a nice day.

[Rishabh Jha]

Hey @Elie Théocari - Sorry for delayed reply. I am glad you were able to have a workaround. I will look into the logs and ask relevant teams why this could have happened. 

[Elie Théocari]

No problem @Rishabh Jha , thank you!

[ManuA]

Hi @Elie Théocari Would you mind creating a ticket for JPD team so that we can look into what is happening with the default contributor role? 
You can create it from here.

[Elie Théocari]

@ManuA I'm sorry, but do you have a direct URL allowing to do that? Last time that I tried, and again I tried right now, I got stuck with an AI agent which chats with me and tells me to visit the same support.atlassian.com URL, with no way to actually create a ticket in the end. I spent much time for no end result and this is frustrating. Thank you.