Rene C. [Atlassian Support] Atlassian Team

Following up on this, I can confirm that when using scoped API Tokens, you can still use Basic authentication, but it has to use a different URL format. This difference in URL is now reflected in the documentation page Manage API tokens for your Atlassian account: How to use an API token A primary use case for API tokens…

Hi, @Samuel Thomas ! This is a community thread and although product managers do check them when making their assessment about changing behaviors, the usual initial point is a feature request/suggestion, which can be found here: JRACLOUD-84617 - Remove shading from image previews. Cast your vote in it and add your feedback…

Remember to add it into the feature request: JRACLOUD-84617 - Remove shading from image previews

Hi, @aadish ! I recently received a support request from another customer with a similar problem. I believe this is related to what @Jorge Belenguer mentioned about scopes generally being meant for OAuth 2. but now that the API Tokens page implemented scopes for API tokens and is also indicating that un-scoped API tokens…

Hi, @Rithi Son please bear in mind that this is a community site, where mostly other users, and community champions exchange information and also where Atlassian shares announcements for changes. If you would like to see something change from its current form, the best place to share your feedback is in our bug tracker,…

Perfectly reasonable request and great workarounds! It is funny when we try to do something with the best intentions (on any level of life) and turns out to be more inconvenient than helpful. Since the best way we have to gather feedback for changes is through Suggestions/Feature requests, I went ahead and created:…

Hi @Dave LIAO Thanks for mentioning that, I configured it on purpose to require users to be logged in as the gadget doesn't work if Jira doesn't know who you are, but I didn't think about it looking "broken" when viewing it as anonymous. I adjusted the filter now and now it will only show an empty gadget instead of an…

Hi @Michael Poremba and everyone in this conversation! I believe all your points are more than fair, and noting that there hasn't been a feature request raised for this, I went ahead and created one: JRACLOUD-84617 - Remove shading from image previews I added a synthesized version of your suggestions there, according to…

I have thought about this as well, and the easy answer I got myself to (without actually knowing the full extent as I am not involved in the administration of it) is that the number of integrations, links, references, customizations and work already done through 15+ years is kind of difficult to migrate, adding to this, it…

@Avery W_ Krouse Our public bug tracker system is a Jira Data Center, so all bugs and feature requests of all our products (whether on-premise or Cloud) are there. 

Hi, @Yatish Madhav ! Dashboards do not have a subscription system to be notified about changes in them, and this is because they don't work based on events, they have a series of gadgets and each gadget displays information based on a JQL query, so every time the page is loaded, or every 15 min (depending on the…

For future reference, this behavior is considered a bug: https://jira.atlassian.com/browse/JSWCLOUD-26934

@Bill Sheboy that's correct, the filters are only considering the resolution "Fixed", as that is the only resolution used to indicate something has been fixed for bugs, or implemented for Suggestions/Feature requests. From your comments, I did some adjustments and additions: * Since using the word "resolved" was too broad,…

HI @Bill Sheboy the gadgets currently only consider one resolution for all the issues, Fixed. All the non-implementation ones (like Timeouts, Obsolete, Won't do, Duplicates) are filtered out. Since there are many feature requests that get bulk closed due to timeouts, lack of traction, being Duplicates, etc. as well as bug…

Hi @Dale Fernandes I know it's been a while since your question but I thought it was important to clarify: Priority schemes where not removed in Jira Cloud, until some time ago they were not part of Server or Cloud, and then they were implemented in Jira Server/Data center. Jira Cloud does not yet have this feature, but…

Hey, @Samuel Stephens ! Thanks for sharing the document! I created this post back when batched notifications where new, and added another comment myself with the procedure to achieve it which is pretty close to what is mentioned in the document. I am not longer part of the Jira Server/Data Center team but I'm glad there is…

For anyone stumbling on this question, this post shares how to create Team-managed projects through REST API: https://community.atlassian.com/t5/Jira-Service-Management/How-can-we-create-a-next-gen-project-via-API/qaq-p/1444092

I believe this is for a different topic. The post is about Advanced Roadmaps teams, not Tempo teams.

I have documented this at https://jira.atlassian.com/browse/JSWCLOUD-23039. Please feel free to add other endpoints you find with the same behavior (the total value missing).

I know it's been a while since this conversation happened, but I just raised a feature request for this purpose and it would be useful to have feedback with your use cases added: https://jira.atlassian.com/browse/JSWCLOUD-22919

I recently raised a feature request for this purpose, please add your feedback for our Product Managers to consider this use case! https://jira.atlassian.com/browse/JSWCLOUD-22919

Hi, Marie-Hélène! Jira does not bundle a feature to clone a project, and neither it has Tests or test plans, and they are likely being provided by a third party app like Xray or Zephyr, this is key because add-on data is usually not stored in Jira itself but in their independent vendor's servers, which means that if…

Hello! The permissions are linked to the Projects, not to the issues, so the issues will respect the permissions of the project they currently reside, meaning that moving an issue from one project to another will make it subject to the permissions of the project where it was moved.

Since bugs are only raised when an issue is replicable (or at least considered a trend) and at the moment I have only encountered a couple of cases a few years apart which are then solved by the workaround, and those cases have also had some form or another of data migration, so this is not considered a bug at the moment,…

I know this conversation happened a while ago, but from support cases I have spotted this happening every now and then, and it was indeed caused by inconsistencies, and the easiest way to solve it is by transferring the ownership of the filter to someone else, and then back at the original owner. If you find this is…

Hi @peter_sarkar ! This issue has been reported to be caused by third party add-ons, so I suggest testing using safe mode as per https://confluence.atlassian.com/display/UPM/Disabling+and+enabling+add-ons#Disablingandenablingadd-ons-Disablingorenablingalladd-ons(usingSafeMode One of the add-ons where this behavior was…

Hola, Luis! El error que te esta mostrando indica que Jira no se puede conectar a la base de datos. Las razones posibles mas comunes para que esto suceda es que: * La base de datos no esta funcionando: asegurate que la base de deatos este funcionando y que el usuario que Jira utiliza pueda conectarse directamente a la base…

If you want steps on how to modify jar files correctly, you can check this documentation page: https://confluence.atlassian.com/adminjiraserver/adding-custom-fields-to-emails-batched-notifications-968669988.html

The query was written in PostgreSQL, so it seems there is a little syntax difference for MySQL, I think you can change the "count(i.*)" for "count(*)" and it will work in MySQL.

Glad you found it and yes, you can use the same procedure to repackage any jar file Jira uses, including language packs!