Alex Expert

Hi @cuong_nt1 This public bug has the reason and the workaround to reinstall apps in the sandbox -> https://jira.atlassian.com/browse/CLOUD-12099 I hope it helps Cheers, Alex

Hi there! Have you found a solution to this? Using a workflow property could do the trick, but it will require adding the same property on all workflow statuses. https://confluence.atlassian.com/adminjiraserver/workflow-properties-938847526.html I hope it helps, Alex

Hey @Dan Chu Data from a completed sprint can be accessed on the reports session of your board — more specifically, the Sprint Report. Give that a try and let me know, Alex

Welcome to the community @Rashidat Busari

Welcome to the community @pr2903 

Hi @Salim Richa I endorse @Viktor Zech [Decadis AG] and @Martin Hilbig _team neusta_ suggestions. For your use case, CSV import is the way to go. Good luck! Alex

Welcome @Alison Milne 

Wow! I'm glad you figured that out.

Hi @Page Partain and welcome to the community. Mail handlers would not transition the issue; however, I am guessing that if your project is JSM, there might be one of the old Jira automation enabled automatically to transition the issue customer comment. Have you checked that? Cheers, Alex

Hi @Lloyd Dahlen and welcome to the community Yes, you can definitely do that, please refer to this link https://support.atlassian.com/confluence-cloud/docs/create-edit-and-publish-a-page/ to have some guidance on editing space pages. Cheers, Aex

Hi @Salim Richa The screenshots donot give a clue to indicate the cause, also the pre-migration logs report issue in other components. Perhaps the post-migration records could indicate what happened 

Hi @Ivan Andrieiev Would you provide a little bit more of context to this question? Perhaps screenshots would help the community to help you. Cheers Alex 

Hi @Thomas Voraberger and welcome to the community Check the history tab of your moved issue and you'll be able to spot the change from the previous transition to empty. I hope that helps. Alex

Hi @Salim Richa Perhaps sharing a piece of the logs or screenshots would shed some light or the issue and help the community to help you. Cheers, Alex

Hi @Ivan Andrieiev If by changes you meant status transition and issue updates, the short and sweet answer is yes. And the reason is that a board is only a view of the issues within the filter. Therefore if your board filter show issues that are also on other filter and other boards, any changes to the issue will reflect…

Welcome @Mark Kinley I hope you have fun learning and sharing your experience with the community! Cheers, Alex

Hey @Manu Tyagi welcome to the community! The issue key is composed by the project key and a sequencial number (Ex. KEY-123). Jira does not allow to handle the issue unless and change how it is created. However, as per your question, when viewing an Epic issue in the screen please note a session named Child Issues listing…

Hi @Ivan Andrieiev Sprints are only available in Scrum Boards, therefore, you can create a single Scrum board with multiple projects on its filter and work on issues from these projects from a single board. When it comes to controls, I’m assuming that you are referring to workflows, if that is the case, please ensure that…

Hi @Manuel The new Confluence credential, applicable to both Cloud and Data Center, is APB-CSA Confluence Space Administration Pro Skills Badge. Cheers! Alex

Hi @Gwen welcome to the community! We are happy to have you here. cheers Alex

I meant great because we know this requirement before triggering a test migration (that's how I learned). However, your point is 100% valid, and from a migration perspective, Jira Business projects will require the JWM product to be deployed on your site.

Hi @Rob Horan I don't think this is a new requirement as I've seen this error before. I believe the newer JCMA version now validates beforehand this dependency, which is great. Cheers, Alex

Hi @Olga Toverovskaya If I am guessing your question correctly, it appears that you are using the Smart Checklist for Jira on your instance, and this is displaying in one project that your client does not need. If my assumption is correct, you might need to refer to the vendor documentation and disable the app for the…

Hi @David Whitlock Please ensure your project exists, the Story issue type is assigned to the project, and the screen assigned to the create issue operation under the Issue Type Screen Scheme has all of the fields (summary and description) you are adding to the payload of your request. Cheers, Alex

It will be on this page https://[YOURSITENAME].atlassian.net/secure/PortfolioHierarchy.jspa

Hi @Clifford Perea , and welcome to the community! My first guess would be your issue hierarchy might not be reflecting the scenario you are expecting. Have you checked the Advanced Roadmaps Hierarchy configuration page? Cheers, Alex

That's awesome @Aditya_miniOrange thanks for sharing the promo code! Alex

Welcome to the community @Hugo King-Fretts

Welcome @Matt McGuinness !

Welcome @DeAnda Clements