Sanam Malleswari Community Champion

Hi @Xiaowen Chen , Welcome to the Atlassian community! Unfortunately, the Jira board Timeline view (like the one shown in your screenshot) is currently hardcoded to only use the following system fields: Start date Due date You cannot configure it to use custom fields in place of those at this time. [JRACLOUD-91648] Allow…

Hi @Shae Theaker Thanks for sharing the screenshot — I understand the confusion. The new Plans Summary feature in Jira Cloud can sometimes look misleading at first glance. Here’s what’s happening in your case: 1) The Status Overview pie chart only reflects issues at the currently selected issue level (e.g., Story, Feature,…

Hi @Piyush Annadate _ACE Pune_ , Thanks. I will try.

Hi @John Funk , Thanks for your response. Could you please suggest any app, if you known any apps?

Exited to use new premium features of JPD.

Hi @Karan Sachdev Thank you for the clarification. You're absolutely right — the colored segments in the backlog indicate the total story points by status category (To Do, In Progress, Done), not the count of issues. Appreciate the correction!

Hi @y.masam Welcome to the Atlassian Community! Hope below ways will be helpful for you. 1) On the Backlog page UI, you can see how many issues are Open, In Progress, and Completed. Just click on each color segment to view the corresponding issues. Please observe below image. 2) You can create filters using JQL (Jira Query…

Hi @Michal Landsman Welcome to the Atlassian Community! Please try below options. 1. Use Built-in Code Block Macro (Basic) Insert the code block macro | Confluence Cloud | Atlassian Support Confluence supports the /Code block macro with syntax highlighting for many languages (e.g., bash, JSON, JavaScript). But it doesn’t…

Hi @Chaya Adams Welcome to the Atlassian Community! Atlassian accounts are global — meaning the same email address (e.g., CFO@company.com) is used across all Atlassian sites. If the CFO already has access to a vendor's Jira, that same Atlassian account can be added to your company’s Jira site. There’s no need to create a…

Hi @Jon Leonard Welcome to the Atlassian Community! Could you kindly provide any images regarding this?

Thank you so much @Maciej Dudziak _Forgappify_ The mentioned app is given the same functionality as per the requirement and it's free.

Hi @Jenni Darroch I just signed up for this study and am completely new to this session. I am working as a Atlassian Engineer Enterprise plan.

Thanks. It's working fine when custom field_11256 value is NO and (1) if no has been.... field is empty. It's showing error as expected(Field is required). But, when custom field_11256 value is YES. It should pass the transition. If this field (1) if no has been.... field is empty or not empty. Could you please suggest any…

Hi @Maciej Dudziak _Forgappify_ Thanks for your reply. Could you please provide the process or links or documents if you have any?

Hi @David Fischer Thanks for your reply. It's working well. I am going to not use JMWE plugin soon due to less usage of this plugin and looking for an alternative way. That will work same as JMWE validator functionality 

Hi @Piyush Annadate _ACE Pune_ Thanks for your response. The JMWE validator function is working fine. Actually, we have very less usage of JMWE plugin. This is the only validator, we should need to configure in alternative ways. We don't have scrip runner also. Please provide any other ways of configuring this JMWE…

Hi @Carlos Garcia Navarro Thanks for your reply. I am not thinking to hire any of companies that handle migrations

Hi @Richard McGhee Is this board filter query will show done issues in result? Is the board using the right estimation field?

Hi @Paurnima Rajput You can get this result by using power shell scripting(or python) with Rest API end points. Getting all users along with that user has access will be bit complex, if there are more users and pages. Try to take one user and having access to which spaces. By using AI you can get general script and adjust…

Hi @Jelena Radan Check if the rollback is still possible If the change was very recent and the page has not been edited multiple times since: Go to ••• (More) → Page History Try to restore a previous version (from before the conversion). This may restore your link names.

Hi @Suresh Chadalawada , 1. Apps or plugin comparability, if there are any internally developed plugins then you will have to find the replacement and add the configurations manually. 2. ⁠user adaptation- not everybody wants to move so need lot more training. 3. ⁠macros in Confluence, there are many use cases that all the…

Hi @Roberto Gimenez Alapont Boards (Scrum/Kanban) are part of Jira Software, not JSM. If your site has Jira Software enabled, you can create separate Kanban boards using JQL filters for each issue type in the JSM project. Steps: Go to Boards > View all boards > Create board. Choose "Create a Kanban board". Choose “Board…

Thanks for the update! Glad to hear the script worked as expected

Hi @Claire Abt Welcome to the Atlassian community! Please try below options. Control Chart (Reports > Control Chart) – If you're using a Jira Software board, this shows how long issues spend in each status. It’s great for spotting delays, especially if items get stuck in “Input Required”. View and understand the control…

Hi @Ciro_Theodoro As per the image, the icons are correct. Firstly, there is a projects/project name/story work item key/bug work item key(with correct icons) If you feel it's incorrect, update the icon: Jira Admin → Issues → Issue Type → Edit → Change Icon.(as you required).

Hi @Adelina Popescu Welcome to the community! When you create a new issue, Jira tries to assign it based on these rules — in order: Is there an automation rule or post function?→ If yes, Jira assigns based on that. Is there a default assignee for the component?→ If a component is selected and it has a default assignee,…

# Jira REST API endpoint for issue creation $restapiuri = "https://jira.atlassian.net/rest/api/2/issue" # Define the issue fields $body = @{ fields = @{ project = @{ key = "LEAR" # Replace with your project key } issuetype = @{ name = "Task" # Replace with your issue type } summary = "Create Issue via Rest API powershell"…

Remove the reporter field altogether if it's not necessary Try below reporter = @{ accountId = "your-account-id-here" }

Hi @Wes Brown You're very close — your script is correctly forming the request, and the authorization is working fine since you're able to retrieve issues. The 400 Bad Request error usually means that Jira doesn't like something in the request body (even if the same JSON works in Postman). Here are a few things to check:…

Hi @[deleted] Try to click on the Manage subscription option under the Support Expires column. You can cancel the subscription. Even, I have struggled recently with the same issue.