Dick Community Champion

Hi @Caitlin Armer Welcome to the Atlassian Community. You need to make sure that the field is available when editing a ticket. To check this, you need to open the screen scheme of your project and dig down through the issue type screen scheme down into the edit issue screen. Your field should be on that screen. Kind…

Hi @Robert Condon You can use the Open status for backlog, and an Approved status as first column in your sprint board. When filling the sprint with the team, they pull from the backlog and place the items in the approved box (you can do this in the backlog view). The metrics you're after would be related to the Days in…

Exactly! And this functionality comes right out-of-the-box. Kind regards, Dick

Hi @binay_yadav Then you have an extra condition using status is Done in the lookupIssues jql. If it is, you want to find its key, then create another issue and use the linked issues selector, set that to relates to, and fill in the issue field to that exact key. Kind regards, Dick

Hi @Tom DiBenedetto Welcome to the Atlassian Community. My best bet for you is to contact the company that makes Zephyr Squad. It might be as simple as a configuration you missed, or it might be a bug when paired to the newest Cloud Jira. Either way, these guys are your best bet to get you afloat. Kind regards, Dick

@Nazar Dunas Hi, and welcome to the Atlassian Community As @Melbrin NGOUILOU stated, this is not possible. Moreover, it would mean finding the parent's children and determine the next index to use prior to actually creating the new sub-task. This puts an extra drag on UX performance, just to make it pretty. Kind regards,…

Hi @Abhimanyu Guleria Welcome to the Atlassian Community You should store the CVE alphanumeric code in a separate (custom) text field called CVE. The scheduled script should not only check your generated label, but also compare the CVE found against your CVE field. You can lookup these tickets, based on: * label =…

Hi @Jacob Jayme Welcome to the Atlassian Community. Please refer to the Atlassian Documentation on which version of OpenJDK is recommended for a certain version of Jira. OpenJDK 17.0.15+8 is in this list too. Kind regards, Dick

Hi @Ecem Buse Yilmaz Thank you for your explanation (both in content and in tone :) ). As a board is merely a pair of glasses to look at a bunch of Jira Work items in one or more projects, it is my guess that you need to copy the content of all projects over to the new site, is that true? Kind regards, Dick

Hi @Saumya Mishra , Welcome to the Atlassian Community If your board filter is not filtering-in sub-tasks, you will not see them on the board. Any quick filters on the board could hold a JQL phrase that would filter out sub-tasks. Please start by providing the board filter so we can look at it. You find this under Board…

Hi @Ecem Buse Yilmaz Welcome to the Atlassian Community Without maintenance, JSM would never get updated. So let's please give the boys and girls at Atlassian some room to get their work done in the predefined time schedule they present you. Respect goes a long way, kind regards, Dick

Hi @오타쿠 Welcome to the Atlassian Community, You can mark fields as being mandatory (they get a small red dot in front of the field) This is done in the cloud version by an admin on a Company Managed Project via: Project Settings - Issues - Fields - Actions - edit field - under actions: press Required. Kind regards, Dick

A team managed, unassigned queue would be my suggestion. Any pre-assigned tickets always run the chance of not being picked-up in a timely fashion. Setting priority to tickets would be possible (even based on time to SLA breach). Make the team responsible for their choices on how to deal with the ticket load and how their…

Hi @Albert Salerno Welcome to the Atlassian Community. I was reading your question and I couldn't help myself from wondering why you would like to automate the assignment of work items to users in the first place. You're effectively "robbing" your team from their team (and individual) responsibility. There is plenty to…

Hi @Filipe Viegas Guerreiro Luis Pires Welcome to the Atlassian Community I notice you've got two transitions between the statuses in your question. Please make sure that both have the correct conditions, just like @Tansu Akdeniz describes. Kind regards, Dick

So we file this one under "Area 52", I guess ;) Kind regards, Dick

Hi Allen, Have you reached out / searched the forums available to users of this app? Kind regards, Dick

Hi @Allen Belonio Welcome to the Atalassian Community! Please provide a picture of your complete automation and a picture of the additional configuration of the "create ticket" action. Kind regards, Dick

Ha, your parent column did the trick here. Glad you worked it out and shared it. If you mark it as answered, other people with similar questions can find it easier. Kind regards, Dick

Hi @Eran Roiter If the roll-up fuction in the roadmap / plans view in Jira isn't what you search for, you could very well use a tool such as JXL to generate the desired listings (sheets). It allows you to create a sum-up line that can even show you the percentage of epics completed. Kind regards, Dick

Hi @Peter Matsumoto Please note that in case you're using any hierarchy of issue types (parent-child relations), that these should be in your csv with parents first, children second as stated in this Atlassian doc. Kind regards, Dick

Looking at your import csv, I think that you should include the parent issues (it appears that you have sub-tasks only) The thing is: during the import process, Jira uses new work item ID's for newly created work items to prevent making work items with the same key. This means that your IssueID column is bypassed during…

Hi @Marta Perez The key instruction in the document you refer to, is this: * Next, confirm the file has all issues listed in order of their hierarchy. this guarantees that a parent is created before a child (sub-task) is created. So it's not the columns that should change, but the order in which the work items are listed…

@Aggeliki K Best approach would be to start setting up using the link above, then post some pictures of your progress. Kind regards, Dick

That should be possible, @Aggeliki K , but keep in mind the sanity of your users. (you don't want to let them search for the correct list to find an option in another) Kind regards, Dick

Hi @Thomas N_ You can use (status in (Done, Planned, "Other Status") AND (assignee = currentUser() OR watcher = currentUser())) Kind regards, Dick Oh, and it's accustomed here to mark an answer as "answered", which makes it easier for people with similar questions to find this answer. Thank you in advance...

The brackets in Shalini's solution influence the order in which the conditions are being processed. Your query is processed like this: Select these tickets: Tickets that are both done and mine, and include all tickets that I watch. This results in area B, E, together with D, E, F, G. So it spans: B, D, E, F, G. Shalini's…

That would mean that there are no tickets that pass your prerequisites. Try watching a ticket, put it in status done and run the query again, you should find that ticket. Kind regards, Dick

Hi @Viktoriia Bashyrova Welcome to the Atlassian community, I'm wondering if your filter names start with characters with diacritics? These can give ordering woes when a browser has to yes/no put stuff in alphabetical order. It would be beneficial to have some pictures of your quick filters, so we can have a bit of a clue…

Dear @Thomas N_ Please note the differences: Correct is: (status in (Done) AND (assignee = currentUser() OR watcher = currentUser())) FALSE is: status = Done AND assignee = currentUser() OR watcher = currentUser()