Zoryana Bohutska _SaaSJet_ Atlassian Partner

Hi @Diego Thanks for the explanation! In addition, I've noticed that the new editor degrades the quality of uploaded images. Can this be changed somehow? Regards Zoryana

Hi @srikanth kocherlakota You will need to do the following: * Setup a staging JIRA server * Take a server backup from the cloud instance(they can also perform step 1 with you as they need to delete any project that you do not need before handing over to you). * Restore the backup on the staging server. * Get Configuration…

Hi @Stuart Haas You can read more about watching, sharing and comments at the Atlassian documentation https://support.atlassian.com/jira-software-cloud/docs/watch-share-and-comment-on-an-issue/

Hi @[deleted] If you on cloud version you can delete version of a page: * Go to the page and choose > Page History * Choose Delete next to the version you want to delete Once you've deleted a version, the other versions will be re-numbered. For example, if you delete version 2, version 3 becomes the new version 2. Deleting…

This app works with Jira Service Desk, Jira Core and Software

Hi @Lacey In such cases our team using different roles for JDS, for example, collaborators. You can read more at the documentation. All is depending on what your needs.

To get data about time in each status you need some app like Time in status for Jira cloud. Also, it lets you calculate the time ticket has been spending in groups of statuses if you need it. And this data is available for export.

Hi @Poojanpreet Singh JSD allows us to select conditions when SLA timer should be on pause.

Hi @Peter Try to set Start event as a first status issue gets once it created. (e.g To Do). Then, cloned issue will be moved to this status, the timer will start. Or, try to edit your configurations for cloned issues. Are you using JSD? If you will need SLA timer for issues from Jira Software (as you mentioned in tags) you…

Hi @Tayo Onabule Do you want to configure SLA for issues at next-gen kanban board?

Hi @fnatsikas To the list of tools, you can consider Boomerang: Reminders for Jira. This add-on helps to create reminders about important issues. You can create a new reminder for an issue and specify the message, time, recipients and recurring settings. Also, there could be a few reminders for one issue. You just need to…

Hi @Asvini Rabindra Automation is exactly what you need. But in case if will need to set SLA timer for issues Jira Software or Core, you can try additional tools, like SLA Time and Report. There is a notification function build-in. Regards

Hi @K Stevenson Did you try audit log? https://confluence.atlassian.com/adminjiraserver/auditing-in-jira-938847740.html#:~:text=View%20the%20audit%20log,-To%20view%20the&text=Choose%20Audit%20Log%20(Jira%20Server,for%20system%2Dgenerated%20events).

Hi @Juan Pedro Silva If you need to get this data now, you can try a solution from the Atlassian Marketplace. For example, one of them is Time in Status for Jira Cloud. It generates reports which show the time individual issues spent on a determined state like Development, QA etc. Also, this app lets you view other types…

Yes, looks like that.. as for me old confluence was much comfortable for work

Hi @Phatchakorn DTX Also, you can consider other apps from the Atlassian marketplace like Issue History. It lets you view all changes that occur with each issue from creation until resolution. This data are available for export as xlsx or csv file. Regards

Hi @as a Maybe, the sprint filtered only parent issue, sub-tasks were not included in filter, that is why time was not recorded. Also, you can check data using the third-party app like a Time in Status for Jira Cloud. It lets you get time your team worked on each issue totally and separately at each status. Additionally,…

Hi @richsnaith You can use a script with the following APIs https://docs.atlassian.com/software/jira/docs/api/7.6.1/com/atlassian/jira/issue/changehistory/ChangeHistoryManager.html#getChangeItemsForField-com.atlassian.jira.issue.Issue-java.lang.String- So you will get the list of all changes for each issue field 

Hi @gayan ganepola If I correctly understand your question - yes, Jira Cloud has the ability to use automation rules https://www.atlassian.com/software/jira/guides/expand-jira/automation

Hi @Rajesh Konda Also, you can try some application from the marketplace for setting SLA time limits not only for JSD tickets but for Jira Software or Jira Core issues. For example, one of them SLA Time and Report. It lets you set conditions for SLA timer according to your project's issue fields (priority, status, label,…

Hello @jean cameron To get data about time in a particular column, you can try such the alternative solution as Time in Status for Jira Cloud - calculates time an issue has been staying in a particular status, and generates the Status Entrance report with the date when the status has been changed. I hope it helps Regards…

Hi @Nish Shah Maybe, this discussion will be useful for you https://community.atlassian.com/t5/Jira-Core-questions/JIRA-Server-to-Cloud-Migration/qaq-p/306490. Or this documentation https://confluence.atlassian.com/jirakb/how-to-migrate-a-project-from-jira-server-to-jira-cloud-779160760.html

As I know issue fields are available for setting and changing only at each project level. Maybe, you can try some automation rules setting.

@james_bailey I agree with you! It would be really useful. If you need quickly create an issue and add basic information, you can consider using a voice assistant as JIVA: Jira Intelligent Virtual Assistant.

Hi @Sandhya Paranjpe You can try third-party solution Issue History. It lets you monitor the full changelog ordered by the time period you need (more than 180 days). Hope it helps Regards

Hi @Oliver Jenkin If you have both projects in the same instance, your Service Desk agents can create and link issues in a Jira Software project and vice versa (if you give them the proper rights to create issues). You will not have to synchronize anything if you have both in the same instance. It does not matter if both…

Hi @Sandhya Paranjpe What tool are you using?

Hi @Magraner Also, in this case, you can consider SLA Time and Report. This add-on allows to add SLA timers for both Jira Service Desk and Jira Software issues. You can monitor data about the status of time limits in the report or on each issue view tab. I hope this info is helpful. Best regards Zoryana

Hi @Yossi Geretz As I know you need to change your Jira Service Desk workflow https://support.atlassian.com/jira-core-cloud/docs/build-the-workflow-you-need/. You should change flow in such a way that each ticket could go from Done status to To Do. Hope it helps

Thanks for the update!