Alex Expert

Hi @Madhu Nukala I am glad you figured that out and posted here your solution to help other members. Cheers, Alex

Hey @Phillip Traynor That's a tricky one, and you nailed it. While creating issues in bulk, Jira only considers the fields available in the create screen. This indeed different from importing from external source. I'm glad you managed to get it working, well done! Cheers, Alex 

Hi @Phillip Traynor You should be good to have your issue created and assigned to a user if you add the user key. I just ran a quick test and got an issue created and assigned to a user using the following CSV file: summary,assignee Summary test,5b59dede106e222d95ea26aa Here is a screenshot of the mapping: I hope it helps,…

Hi @Madhu Nukala Migrating Jira from Server/Data Center to the cloud is subject to several challenges. Your instance and cloud site might be affected by the known issue described on When migrating from Jira Server to Jira Cloud via XML backup, the restoration fails with the error '[GenericDelegator.makeValue] could not…

Hey @Ashish Pandey Jira Cloud will require the Team field to be added to the screen that Jira uses for the Issue Layout. It was in the default screen in my tests, but on your site can be any other screen. Once you add the Team field to the screen, you can achieve the same results in Jira Cloud as well: Please be aware that…

Hi @RSP This is an excellent question! It comes down to the user experience and consistency while creating, editing transitioning a Jira issue: Validator * It prevents the workflow transition from happening if criteria do not match * Display a workflow error message and request the user to fix the field * If the same field…

Hi @Andrej Freeze greenique I don't know a tool that would replace those workflow post-functions in bulk, however, you can give a try Microscope to get the overall insights into your Jira workflow functions and workflow that you will be required to update. Additionally, for replacing those functions for Scriptrunner…

Hi @Ashish Pandey! I did a simulation for your scenario using the Team custom field in tasks and sub-tasks in Advanced Roadmaps, and you are right. By searching for those issues in the Issue Navigator, the column Team shows values. Therefore, I changed the Screen Scheme to add the Team custom field in the View Issue…

Thanks, @Oliver Scott-Hughes (CX), it worked perfectly! A simple addition based on my use case. Since I am using JSM Data Center, this API is still experimental, thus another header was required. Headers box 3: "X-ExperimentalApi" Headers box 4: "opt-in"

Hi @Oliver Scott-Hughes (CX) This solution is pretty neat and will solve my case as well. Could you share an example of the Webhook URL to send web request ? I did not manage to identify what is the API that provides the organization data. Thanks, Alex

Hi @[deleted] ! Based on this answer, I believe it not possible still. https://community.atlassian.com/t5/Jira-questions/How-to-modify-WYSIWYG-editor-in-cloud-hosted-Jira/qaq-p/1035510 Cheers, Alex 

Hi @Kat Warner I want to share my experience following this study plan to take the ACP-200. Before I came across this plan, I started with the Confluence Administrator Certification Prep course, but there were many areas that I did not know. After giving a stepped base and reviewing Confluence Server…

Hi @Jonathan Steele and welcome to Atlassian Community You can restore access to your admin user by changing the admin password from the DB with the following steps: * Connect to Jira database * Locate admin user_id * from cwd_user where user_name='<admin_username>' and directory_id = 1;select * Update password (example…

I loved this plan and I am following it to take my ACP-200 exam int the end of this month. Thanks for putting this together. Cheers, Alex

Hi @jira_admin_cu My suggestion is to add the post-function Update Any Issue Field (JSU) on the transition to "Ready For Review" status and define the value of the custom field as %%CURRENT_DATETIME%% Every time the issue transition to Ready For Review the date will be logged and you can JQL this field. I hope it helps,…

Hi @Monika Goel and welcome to the Atlassian community! Option #1 will certainly run into issues due to changes in database structure from version 7.3 to 8.13, not only from Jira itself but with apps as well. So don't do it. Since your use case includes not only Jira version upgrade but also, database change, I would…

Hey Mike! Yes, that's is my best guess. Because in all of my tests, this the Epic Name popped up as required to fill up. But on the other hand, you have it with the correct value on the issue view screen. So, have you explored a possible browser cache issue? Thanks, Alex

Hi @bhaueter It will depend on how your company wants to scale Scrum across multiple teams. A common approach that I have seen is not actually tied to projects but tracking teams with different boards. This picture might give you a broad view of what I am referring to: Please note that regardless of the projects, teams…

Hey @Mike Buretta When you move the Story to be an Epic, have you noticed a screen to inform the Epic Name? While converting any issue into an Epic, Jira will request you to inform the Epic Name. If so, there might be a chance that the old Epic Name is cached in the browser. Did a couple of tests myself and also executed…

Here is my suggestion: - Create a new field configuration based on the current field configuration used for the project and turn the Tempo Team field required - Create a new field configuration scheme and add the recently created field configuration as default. Here I am assuming all issue types of your projects will have…