Fabio Racobaldo [Catworkx] Community Champion

Hi @Ömer Gündüz , @Gor Greyan has right. As possible workaround you can setup a temporary calendar, switch to the new calendar the half holiday day and then come back to the original one. This is the only way that I know using builtin features. Hope this helps, Fabio

I already completed all learning paths so no enough kudos for me :( 

Hi @keerthika Narra , my suggestion is to collect all these users in a specific group and then send a notification email trough the following feature https://support.atlassian.com/jira/kb/send-an-email-notification-to-all-jira-data-center-users/ Hope this helps, Fabio

Hi @Shaun , if your license has expired how can you work on a JIRA 9.12.1? Is your license an old server license? Btw, for my knowledge the only one solution is to upgrade your jira. Fabio

Hey @arnaud , If you contact a partner you could have a discount. If you want, I can support you on my side (please send me an email to fabio.racobaldo@herzum.com ) BTW, you can request a quote to Atlassian using the following guide: Create a quote Currently, you need to contact us to create a quote. To request a quote, *…

hey @Macors Romain , please ensure that user that your are trying to add to your space has permission to access your instance. As confluence admin go to global permission and verify that user has "Can use Confluence" permission. That should be the reason, Fabio

hey @DEEPAN CHAKRAVARTHY M did u check it?

hey @Macors Romain , please check that user directory is importing users from AD and that in the new instace you correctly setup global permissions so that users can use that instance https://confluence.atlassian.com/doc/global-permissions-overview-138709.html 

Hi @Manjunath Matta , first of please check your Atlassian email preferences. * Go to https://id.atlassian.com * Sign in with the same email used for the invitation * Go to Account Settings → Email → Email Preferences * Make sure Product Invitations is enabled If it is disabled, invitation emails are blocked. Hope this…

Hi @Macors Romain , if you exported space from an instance and import into a new one, probably the user ids are different so, as local admin, you should setup permission on new space and try again. This should fix your issue. Hope this helps, Fabio

Hi @Prashant Sarwal , please follow this guide in order to activate Rovo for your instance https://www.atlassian.com/software/rovo/guides/admin-guide/rovo-activation#confirm-activation Hope this helps, Fabio

Hi @MMedina and welcome, first of all please check with an admin if a permission change has been performed on that project so that you can't see it but it still exists. If it is not a permission issue, please take a look to the following…

Hi @Jayaram Boya , please could you provide us more information? Please check your write permissions and if there are some specific branch permissions set. Hope this helps, Fabio

Hi @Akhila Arsan , I found this bug on the Atlassian backlog https://jira.atlassian.com/browse/CWD-6497 It seems to be a bug fixed on version 7.1.6. My suggestion is to upgrade your crowd and try again. Hope this helps, Fabio

hi @JaneBrandhub , please check the workaround provided by @rwillia2 

Hi @Henry , if you are on a cloud instance you can't add a javascript. If you are on a DataCenter version you are trying to use a JIRA event on confluence side and it is not correct. Hope this helps, Fabio

Hi @Arkadiusz Wroblewski , this a very useful feature. I just voted it!

Hi @Sebastian Stepponat , you can massively update tickets using cvs on Data Center instance. In order to do that you need to use Issue Key column (and maps it to issue key field) so that jira understand that it is an update an not a create. Please take a look…

Hi @Menno van der Heijden and welcome, can we close this thread? Fabio

Hey @Raheem Pillay , it means that Time to resolve is Resolution Date - Creation Date - (time in status Pending). Moreover you need to check the calendar. When a ticket is out of working hours it is automatically stopped. Hope this clarifies, Fabio

Hi @Genna Reingold and welcome you could try to setup the following option in order to overwrite your local tags Open SourceTree -> Terminal and run the following command : git config fetch.prune true git config fetch.pruneTags true Hope this helps,Fabio

Hi @Laura Jimenez Valencia , please take a look to the following article https://support.atlassian.com/platform-experiences/docs/smart-links-from-jira-and-other-products/ Here some reasons * the user does not have permission to view the linked content, * or the system cannot resolve the link, * or the user’s Smart Link…

Hi giuseppe.corsello@nnamu.com , as specified here https://developer.atlassian.com/server/jira-servicedesk/rest/v1004/api-group-customer/ customer creation via REST Api does not cause invitation email to be sent to the newly created customer. The customer can still log in later by using “Forgot your password” or by having…

Hi @Zekli DMS and welcome, in order to have an overview about SLA configuration please read the following page https://support.atlassian.com/jira-service-management-cloud/docs/create-service-level-agreements-slas/ About pricing please take a look here Hope this helps, Fabio

Hi @Dharmendra Bhankhodiya and welcome, please could you better specify your need? Fabio

Hi @Michael Montanye and welcome, could you try the following format? {jiraissues:columns=[list of columns]|url=https://[server url]issues/?jql=project+in+%28PROJA%2CPROJB%29+AND+fixVersion%3D%22[fix version]%22} Hope this helps, Fabio

Hi @Mick and welcome, there are no active incidents on confluence. Is it a free instance? When was the last time you accessed the instance? Free instance with no access for a long time could be automatically deativated by Atlassian. Hope this helps, Fabio

Hey @Raheem Pillay , please share your SLA configuration in order to better understand your scenario. BTW, based on that time to resolve avg is based on creation date and resolved date. Please take a look also to your calendar/s in order to fully inderstand when SLA is in progress or stopped. Fabio

Hi @DSI SOCE , first of all you need to connect to crowd with an admin account and try to check your credential in the directory (we don't know if your crowd is connected to an external AD). Moreover please check that user has grants to access application. Hope this helps, Fabio

Hi @Vikas Mahajan , please check the API token scope (https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/ ) in order to be sure that token is able to create items. Hope this helps, Fabio