Dick Community Champion

@AkeshiAtoriato Welcome to the Atlassian community. If you feel that a question has been answered, you also can vote for it as well. Just use the up-triangle next to the Accept answer button of the comment you want to support. Kind regards, Dick

Hi @Ramesh Krishnan , If a story is in more than one sprint, the field sprint has more than one element (it's a comma separated string of names that has more than one entry). You can check this visually, or by means of automation: * Just counting the number of comma's in the field, if it's more than 1, you have a story…

Hi @Jason Bullock Welcome to the Atlassian Community Normally, these plug-in specific pages with property data are accessed using the Cogwheel - Applications - left menu. You would need administrative access for this menu. It looks like this (This is our instance, where you see the GIT Integration for Jira plugin pages…

Hi @David Nickell There are three levels of admin in the Jira Environment. From top to bottom: * Organizational Admin * Jira Admin * Project Admin Your link concerns the top-level admin interface. It is yet unclear which level @Anurag Bharati is working with. It could explain the discrepancies. Kind regards, Dick

Hi @Indrasena Welcome to the Atlassian Community Thanks for reaching out, but this is not the correct forum to apply for a job. LinkedIn would be more effective for this purpose, as this forum is moderated to be strictly questions about problems that users encounter when using Jira. Thank you for understanding, Dick

Thanks @Dommalapati Chandrababu Naidu for your patience with me :) Each automation needs a trigger. You have basically two options: * A manual trigger from the ... more menu when the test story is selected. * A trigger initiated by a change in a field value of the test story. In the former, your tester A should know where…

(please set me straight if I'm at error) So you have a person A who is performing a test that is described in a Jira story that is reported by person B. If person A finds a bug during testing, you want an automation to fabricate a story assigned to person B, so he/she can amend the code that was originally put up for…

Hi @Anurag Bharati The token you use holds the same permission level as the user that created it. I can imagine that user management calls requires admin permission. * Does the token that you use have such (user derived) permissions? Kind regards, Dick

Hi @Dommalapati Chandrababu Naidu I'm afraid your question needs a little work in order to get the response it deserves. Could you rephrase it so that your intention is more clear please? Kind regards, Dick

Hi @Gee Espiritu , New projects for a team will be inserted into their project, which is visible on their board. Remember that work should be entered into the Jira Space of the team that actually does the work. So if team B supports an epic of team A, team B creates the work item in their own Jira Space and link it to the…

Hi @Gee Espiritu Welcome to the Atlassian Community At our university, we do the latter: We have designated teams that each have a Jira Space to track their issues of the projects they do work for. The work items can be of all issue types, as we use components to discern the projects. That way, you can still have the whole…

Hi @Maria Cracco Since your question is a bit abstract, my answer is too. Big sigh of relief: you can use Jira Automation to do the job. But in order to process your tickets from Claude Code, you need to: * Have a trigger to start the automation. This could be a change in a certain field or even a custom field on the…

Hi @Keny Jimenez Welcome to the Atlassian Community I can give you some pointers as where to find Jira activity in Jira Data Center even when there are no users connected. There are a number of automated scripts that fire-up regulary as these are cron based. Their function is to 'cleanup' your instance and keep it running…

Hi @pisov Best you take this up with the developers of the AIO plugin to expand their product with a persistent project selection feature. Kind regards, Dick

Hi Marianne, Welcome to the Atlassian Community Rovo is a continuously learning AI. Depending on the data it gets to learn from, it learns different things and situations when to apply the learnt stuff as an answer to questions posed by humans. The above means that answers can vary when questions stay the same. Also,…

Hi @Mahanth Prudhvi P AI is a great tool, but it needs to be fed in order to shine: You need to feed it data first. In your case specifically (if you want it to know "impacted areas"), you need to have it "learn" what you consider an impacted area. What Rovo, Atlassian's AI is doing, it is making use of the huge Atlassian…

Hi @Srushti Jadhav Nope, only one transition screen is possible (out-of-the-box). What you -can- do is vote for this feature: JRACLOUD-12244 

Hi @Srushti Jadhav , Sadly, the comments field is there by default, on every tab you create too, it's hardcoded. Kind regards, Dick

Hi @Charlotte Watson Welcome to the Atlassian Community Please share with us a picture of your setup of: Board Configuration - General It might hold the answer to your disappearing stories. Kind regards, Dick

Hi @Mohit Chawla Welcome to the Atlassian Community. Please provide pictures of your automation, with the details of important steps and audit log, so we can tell you which part is not running as you should like. It makes answering so much easier. We're all friendly over here. Kind regards, Dick

Hi @Srushti Jadhav Welcome to the Atlassian Community! What you could do is to create a new text field (like: final comment) and give this field: * A description, that provides a hint to what the person filling in the field should write. * Or maybe present the user with a prefilled field by setting a default value for this…

@Trudy P Claspill Fields of a modified work item display only the modified content correctly after a re-fetch. The action of modifying a field’s value is done in the database, not the work item “copy” that is used inside the automation. The modified field value needs to be re-fetched to work with it.

This would be true only after a re-fetch… 

Hi @Jan Nolens , remember that execution of branches is done in parallel by Jira’s automation engine. There’s no way of telling the order in which they are executed nor finish. The limbo state resulting can in some cases be avoided by either separating them from each other, or by using a re-fetch of the current work item.…

To get such a valuable message across, one should best: 1. Address the real decision makers (not take things out on devs) 2. Use an appropriate channel (not misuse these help-giving forums) 3. Bring as many as possible compelling arguments to the table I’m not thrilled by the upcoming changes in menu structure either, as…

Dag @Jan Nolens In your automation, you have a non-descript trigger followed by a branch that is allowed to change the status for both “is duplicate” and “duplicates” conditions. That in itself generates the infinite loop if the automation is allowed to start itself. How to avoid this from happening? You should construct…

Hi @Tau Slater Welcome to the Atlassian Community We're here to help, but in your instance, I would first suggest: Have you contacted Atlassian Support via the link? They're fine folks, that do their best to make Jira work the way it should. So letting them know that something is wrong in your instance is the first step to…

Hi @Steve Hayes Welcome to the Atlassian Community I believe it's part of the good practice to keep Jira versions in their own dedicated folder. So when you update, files are added to the new folder with the correct version number. The modified files are the configuration files that point to the location of the version…

Hi @Steve Krummes Welcome to the Atlassian Community When you use a scheduled automation, you are allowed to put in a JQL query. All the Jira items found in this query will be subjected to the remainder of the automation. So if that query were to find all epics that are due within a month, you can check each of these…

instead of "{{issue.parent.customfield_43602}}" I always use {{issue.parent.customfield_43602.asJsonString}} described Here.