Comments
-
Hello @Jared Elliott Welcome to the Atlassian community. Please show us the rule you have constructed and the details of the step where you are creating the Confluence page.
-
Hello @Garth Smitman In my Jira Cloud environment for the Two Dimensional Filter Statistics gadget I see the built in Fix For Versions field and the custom Versions type field that I created and named Affected Versions. Is your Affected Versions field a Versions type field?
-
Hello @Dave Kuipers Welcome to the Atlassian community. There are two ways to set requirements on transitions - Conditions and Validators. If a Condition is not met, then the transition will not even be presented to the user. With Validators, the transition is available. The Validator is applied when the user clicks the…
-
If it is unchecked then you will not get emails, via the Notifications Scheme, for any issue changes triggered by you and that includes issue creation. If you are an admin for the project you could circumvent that by creating an Automation Rule to send you email for issues you create.
-
This limitation applies only issue types that you add to level 1. When you create new issue types in Jira they are created as either standard issue types (level 0) or subtask issue types (level -1). There is no option to create an issue type that mimics the Epic issue type. Your new issue type for "legal holds" was likely…
-
Hello @Carissa Le Welcome to the Atlassian community. The issue types available initially depend on the Project Template you used to create the project. Not all project templates include the Epic and Story issue types by default. Do you recall the project template you selected when creating your project? Also, have you…
-
This is true if the projects are Company Managed projects and are, in fact, sharing the workflow. You need to confirm that the projects' Workflow Schemes are in fact using the same Workflow entity, versus the same apparent workflow but defined multiple times in separate Workflow entities. Team Managed projects do not share…
-
Hello @Kaupo Kõrm Welcome to the Atlassian Community. In that type of project (Work Management) issues in the columns with green statuses are hidden from the board display automatically when they have been in that column for 14 days or longer. This is not a configurable option.
-
Hello @Rogerio There currently is no tool for Jira Cloud for assessing usage of third party apps. You will need to reach out to the vendor of each app to find out if they have any method for assessing usage.
-
Hello @Maciej Kaniewski Welcome to the Atlassian community. Are you working with a Team Managed project or a Company Managed project? That information will show at the bottom of the navigation panel on the left. Is there an Automation Rule running that is automatically pulling the issue out of the inactive sprint? Check…
-
Hello @Phil Use sprint in openSprints() https://support.atlassian.com/jira-software-cloud/docs/jql-functions/#openSprints--
-
Changer le filtre du tableau pour trier par statut est une mauvaise idée. Si le filtre du tableau n'utilise pas ORDER BY RANK, vous ne pouvez pas faire glisser les cartes de haut en bas dans les colonnes ou dans le backlog pour les redéfinir. --- Changing the board filter to order by status is a bad idea. If the board…
-
Here is one change request related to support multiple issue types as Epics. There may be others. https://jira.atlassian.com/browse/JRACLOUD-80492
-
Have you checked your Personal settings to confirm this box is checked?
-
Not with a single API call, no. You would need to execute multiple API calls to retrieve the child subtasks of the parent issue and then transition them.
-
It sounds like you have created a new issue type named "legal hold" and added it to your Issue Type Hierarchy at the same level as the built in issue type Epic. Is that correct? If so, then the board is currently working as designed. The Swimlanes Based On Epics option works only with the built-in Epic issue type. I have…
-
I have never noted how this behaved in the past. Atlassian posts messages weekly about changes in functionality. You might want to look through them to see if there is a changes that seems applicable. https://confluence.atlassian.com/cloud/blog/2023/09
-
You can open a support case with Atlassian Support to find out if such a request already exists. https://support.atlassian.com/contact/#/
-
I don't know enough about ScriptRunner to know if you can accomplish that with that app, but you could accomplish that with an Automation Rule.
-
You don't need to create a new project for this. Yes, if you have the Jira Software product then you can create a Saved filter for the Work Management project and create a new board from that saved filter. However that board cannot have its Location set to the Work Management project, and such a board presents quite a bit…
-
It is possible in an automation rule to add a Condition to check a field, and if the field meets the condition then you can follow that with an Action to Create Issue. However, using a single rule to iterate through a multi-selection list to find out which values are selected is more challenging. It is not something I've…
-
None of these screen images are of the Permissions Scheme for the project, showing the groups granted the Assignable User permission, nor the Global Permissions showing the groups that have the "Browse users and groups" permission.
-
Hello @Peter Davis Can you show us the setting in the Notification Scheme for the Issue Created event? Can you confirm for us that your Service Management project is a Company Managed project as opposed to a Team Managed project? That information will display at the bottom of the navigation panel on the left when you are…
-
Hello @Josh Kelley Welcome to the Atlassian community. The Business/Work Management project filter does not appear to currently support a User Picker (Multiple) field at this time. It does support a User Picker (Single) field. I have not found a change request in the public Atlassian backlog for that, but you could ask…
-
In that case the subtasks will not be visible as separate cards. It appears that for every Swimlane setting except Stories you need to include the parent issues of the subtasks in the board filter. Without that the subtasks will not display. Did you change your Swimlanes setting compared to last week?
-
@Bill Sheboy should get credit for this answer. :-)
-
Regarding your API issue, HTTP error code 400 is "bad request" not "bad gateway". Those are two very different errors. Which one are you actually getting. Regarding extracting data from your separate database to use as input to Jira, you won't code that interaction using either the Jira REST API or the JiraPS module. That…
-
@Uri Shavit (EDIT: I mentioned the wrong person in my initial response.) You may not have a Global Transition (an arrow from the word "any" to the "done" status). In a workflow diagram each arrow is a transition. Each arrow points to a Status. If the arrow comes from the word "any" that means you can transition from any…
-
If the JiraPS code is working for you, then what exactly is your question?
-
Hm, this is an odd one. Have the folks experiencing the problem tried the same thing in another browser, and find they get the same error? Has your Jira Admin, Site Admin, or Org admin already contacted Atlassian Support directly about this?