Fabio Racobaldo [Catworkx] Community Champion

Hi @sarathgd , JQL are used to retrieve tickets and not for other items so there is no way to have those information through a JQL. You can extract tickets that are associated to future sprints through issue in futureSprints() JQL Hope this helps, Fabio

Hi @Jonathan Cooper , the secondo command is wrong. In order to restore DB from dump you should use "mysql" and not "mysqldump" command. mysql -u confluence -p confluence < D:\mysql-backups\mysql5.7-nofurthercollation.sql Please could you check? Fabio

Hi @Sachin Pattankude , welcome to the Atlassian community! As said by @Mayur Jadhav there is an active incident on Confluence cloud. You can subscribe so that you will be notified about the updates https://confluence.status.atlassian.com/#subscribe-modal-8rpbybnx2vjw Fabio

Hi @Dirk Vansina , that point is one of the most discussed in the community! From my perspective, the best way is to have a workflow that, in case of failure in QA, ticket can be moved back to dev in order to fix the issue. Pro of that approach is that history of ticket, including comments, branch/code/commit and all other…

Hi @Veronika Davydova _ Shiji , welcome to the Atlassian community! Are u using a supported browser? https://support.atlassian.com/atlassian-account/docs/supported-browsers-for-atlassian-cloud-products/ It seems to be a clinet side error so there are no error on Confluence side. Fabio

Hi @Saira , I think you are referring to JIRA and not to Confluence. Btw, you need to manage "Assign permission" in the project permission scheme so that just the assignee can do that. Hope this helps, Fabio

Hi @Gaby , when you are on edit view, instead of clicking publish you should go to ... and click to "Publich with version comment". A popup will appear and you will able to add your comment. Please take a look to the following screenshot : Hope this helps, Fabio

Hi @kang , welcome to the Atlassian community! Sometimes it happened also for me. If the users come from AD, you can try to setup again the AD integration on the User Directory side and disable the current one. Hope this helps, Fabio

Hi @Ahmet Oezdemir , here the addon pricing based on users https://marketplace.atlassian.com/apps/1211022/links-hierarchy-full-dependency-viewer?hosting=server&tab=pricing Fabio

Hi @Thomas Lanz , welcome to the Atlassian community! Please could you provide more information about the error occurred? Fabio

Hi @Simcha Kuritzky , are u using an external app like https://marketplace.atlassian.com/apps/36199/cenote-lockpoint-attachment-check-out?hosting=cloud&tab=overview? Fabio

Hi @Jan-Luca Lobers , welcome to the Atlassian community! If your link have been hardcoded in your pages you can't change them in one shot. Fabio

Hi @Ajinkya Paradkar , please could you check if, on the destiantion project/issue type workflow there is some validator or post function on creation? Fabio

Hi @Vishal , you could avoid that just removing those users from create issue permission in your jira software project. Fabio

Hi @Darren , you can retrieve all the operation done through the audit log https://confluence.atlassian.com/adminjiraserver/audit-log-events-in-jira-998879036.html Hope this helps, Fabio

You can create a page tree with inside files

Hi @Saira , a workflow validator can help you on that during transition opertion. Btw, a ticket could be reassigned through an assign operation that doesn't involve a validator. 

Hi @Ronald Kopecky , in my opinion the best way to do that is through a move operation. JIRA assistant is necessary beacause, changing the issue type you could have impact at field and workflow level so you should provide some information during that operation. Hope this helps, Fabio

Great! Thanks for sharing

Hi @Shilpa_R , welcome to the Atlassian community! You can try to use openSprints(), closedSprints() and futureSprints() functions. sprint in openSprints() : it filters issue associated to all on going sprints. More information available at the following…

Hi @Edcs Pvt Ltd , SLAs are for project basis so you need to access each project and check the SLA configuration. Hope this helps, Fabio

Hi @Patricia Bermejo , welcome to the Atlassian community! You can't hide specific sprint to some people and, from agile perspective I don't understand the use case. BTW, you can hide tickets using Issue Security Level so that just some people can view those issues. Fabio

Hi @Jovanka Jovicic , did u try to reindex your project?

Is the completed status on the last column on the right of your board? The total of story points should be the sum of all ticket that are in a status mapped on the last column on the right. Please could you confirm?

Hi @Vin Aggarwal , you could try to add the following condition to your current JQL : ... AND issue in linkedIssues("YOUR SPECIFIC TICKE ID") Hope this fixs your issue, Fabio

Hi @Jovanka Jovicic , please could you share information about the changes? In order to provide you a solution we need to know what you changed and your current implementation. Fabio

Hi @Denis Uschapivsky , my suggestion is to manage all these things in a single service desk project and put in place a different access to tickets based on Issue Security. Using that approach Task for Analyst will have a specific issue security so that these tasks could be visible just to member of that team and the same…

Hi @Rachel Foley , you need to setup permission scheme/project role so that user has access to a specific project. Hope this helps, Fabio

Hi @Jerry Etta , Take a look to the following video https://www.youtube.com/watch?v=Nw0VdpcfbPE It should help. Fabio

Hi @Isaac obakpee , welcome to the Atlassian community! Try this course https://enable.atlassian.com/student/path/815443-jira-fundamentals Fabio