Ana Vitória Selista Specialist

Same here. I just drop it 

Fo me it was the other way around. I added a Scriptrunner post function using the new editor (as rules) and published. But when I switched to old editor it was gone. 🫠 And then I switched back to new editor and it was there.

There’s so much going on and at the same time we lack basic ways of working and integrating this functionality.

That’s true, there is a lack of documentation, even about API endpoints for Teams. But I don’t agree with your vision about working with teams in automations. Have you tried? Because there’s nothing you can do. You can’t create conditions about team field, can’t search for members in a team, and the only way you can work…

Not to mention that Teams are global across the organization, so if you have more than one Jira instance, your teams are shared whether you want it or not.

Just signed up. Let’s make history!

Hi Krisztina, You can archive that using Security schemes, in the configurations of your project. I suggest the article: https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-security-schemes/ Basically, you can configure security levels for your items. Once a level is set to an item, only the people…

Olá Mateus, tudo bem? Unfortunately, Jira’s native JQL does not support comparing date fields (e.g., dueDate - created < 3) or referencing the sprint’s start date directly. A more scalable and accurate approach would be using the Jira REST API with a Python script. Here’s the idea: * Use the API to fetch all sprints from…

No worries, it happens! Glad I could help.

Hi David! When you click on “+ Create” on the board it should appear a icon for you, for task type is a blue icon, you can click and change it, therefore changing the work item type (Epic has a purple icon by default). Or, you can create your issues directly on the blue “Create” button on Jira main menu, on the right side…

Hi Tamas, welcome to the community! In your image, I see the columns in alphabetical order. The only problem is you are the first one, and you shouldn’t. I’m guessing this is because of the filter applied at the top of the board, for your tasks. Could you try removing it? If that doesn’t work, please share the other…

Hi Kate, I’m not sure about doing that using the jira-python library, but I can help you with Python by accessing the Jira REST API directly. To update a project role, you can use the following template: import requests from requests.auth import HTTPBasicAuth import json url = "https://your-domain/rest/api/2/role/{id}"…

Hi Jessica, Epics do not appear in the Scrum backlog or board like other issue types (e.g., stories or tasks). Instead, they show up in a separate Epic panel on the left side of the backlog. Jira treats epics as containers for other issues, not as sprintable items, so they don't appear in the main backlog or board.

Online attendee here! I'm excited to hear more about Rovo, AI advancements, and what’s coming next. And of course, what’s in store for Williams Racing this year!

Hi Venkatesh, Each sprint is tied to a specific board, and since you have multiple boards for different sub-teams, the best approach is to implement a custom field to designate the responsible team when an issue is created. You can either have users set this field manually or automate its population based on predefined…

Hi Roxsanne! Adding a new status won’t affect existing statuses or issues. It won’t delete issues or change the status of any issues. The only impact is that your new status will take effect once you publish the changes. Jira shows this message whenever you edit a workflow because you have the option to save a copy of the…

Oh yeah, when you use JCMA (Jira Cloud Migration Assistant) for migration within the same organization, it duplicates the teams since teams are tied to the organization, not a specific instance. There's a ticket about it here: https://jira.atlassian.com/browse/JRACLOUD-93358

Hi Patricia, It looks like you're dealing with duplicated teams, not just in the dropdown. As you can see, "CS2G" has 11 members in the first option and 10 members in the second. Also, the icon colors are different, meaning they are separate teams. You can check all your teams and manage the duplicates by accessing "Teams"…

Atlassian's official documentation does not list Windows 11 as a supported operating system for running Jira versions 9.6 and 8.22.1, or Confluence version 7.9. The supported platforms typically include various versions of Windows Server and specific Linux distributions. ​ While it's possible to install and run these…

Hi Michael, Are you referring to a checklist plugin functionality? Could you provide some images for clarity? Thanks.

Hi Ashley, You can find error logs in the jira-logs file, I think. In your case, I would recommend creating a copy of this field configuration, reviewing the required fields, and applying the copy only to your project. This way, you avoid setting a field as required when it might not be present on the screen. This issue…

Hi Amy, This is not possible with native JQL, as it does not support searching based on parent criteria. However, if you have ScriptRunner, you can try this: (issueFunction in subtasksOf("type in ("story", "bug") and status in ("YOUR_STATUS", "YOUR_STATUS_2")") and status != Done) OR ( issueFunction in subtasksOf("type in…

In Jira, hierarchy follows three levels: Epics (1), standard issues (0), and subtasks (-1). You can't display Epics and their subtasks together without their parent issue (level 0), as this breaks the hierarchy structure.

Jira dashboard gadgets are primarily based on filters. Since filters always return issues, we can't directly retrieve a list of users. However, we can get a list of issues assigned to users. In your case, issues assigned to active users. - If you have Scriptrunner, you can use the following JQL query: assignee not in…

Hi Dsaveri, Jira issues are always assigned to individuals. If you have an issue where person A executes X and person B executes Y, that means you actually have two issues, one for each. However, if you need to track work at a group level, here’s an effective approach: 1. Use Jira Groups for User Management Jira groups act…

1. The configuration affects only the workflow where it is applied. In Jira, each issue type can have its own workflow, but workflows can also be shared across multiple issue types and projects (except in team-managed projects: Atlassian Support). If your workflow is dedicated, the changes will not have a global impact.…

Hi Madhavi, if you have Scriptrunner, use the following: status = "Ready for Testing" AND issueType = your_issuetype AND issueFunction in hasSubtasks("resolutions is empty") This JQL finds issues of a certain type that are in the "Ready for Testing" status and have at least one unresolved sub-task. Hope it helps!

Hi Carsten, I believe you could archieve this by using conditions in the transitions to restrict them. To do that, you can use "User is in any project roles", them select all project roles that should be able to see the transition and leave "PO" out. I suggest you use project roles for this, as it is the easier solution,…

Hi Yina, To restrict actions when the issue is in a certain status you can use status properties: https://support.atlassian.com/jira-cloud-administration/docs/use-workflow-properties/ I believe what you want is to remove the "Log work" option when the issue is in "Done" status. For that you need to edit your workflow,…

Hi Okady, Please go to your project settings -> Features -> Disable "Releases" and then enable it again. This appears to be a bug, as reported here: https://jira.atlassian.com/browse/JRACLOUD-93444. You can vote and watch to see the progress. I tested it in my environment, and the workaround seems to work! Hope it helps!