Ignacio Pulgar Expert

Hi @Parrish Pope , In that concrete example, maybe you can add this condition to the Insert Automation's JQL: ...AND "Epic Link" is EMPTY That way you will remove Stories from the first level which belonged to an Epic, therefore removing duplicates. Depending on your exact use case, it might work for you, or maybe that's…

Hi @Poojaa Sudhakaran , I think @Egor Tasa [ALM Works] has probably used the Structure Notes Column for having a column with the same value than what it is returned by your Issue Picker field. Just substitute Notes with the name of your custom field with no blankspaces. I think it is Initiative Link, so use inititativeLink…

Oops! My fault! Issue Picker fields do not add issuelinks natively. I must have been confused with the way other kind-of "issue pickers" work, like vLinks or Easy Links for Jira. With no need for additional addons, maybe a ScriptRunner's Script Listener could be set to also add an issuelink with the issues added to an…

Hi @Poojaa Sudhakaran , As Issue Picker fields also put an issuelink in place, I'd suggest following these steps (I'll assume that the type of said issuelink is "relates to", although it might need to be adjusted for your case): * Enter the Structure Board and add an Insert Automation based on the following JQL: type =…

Those are awesome news! We've just planned the upgrade! :) Thank you!

I have reproduced the blank and not-working result on a JSW Data Center 8.2.3 instance with Structure 5.6.3. The working solution I placed here has been achieved on a local installation (in my laptop) of Jira Server 8.6.1 with Structure 6.0 EAP. I confirm in this instance the following syntax works like a charm:…

Hi @Egor Tasa [ALM Works] , I suspect it might have something to do with the way Structure process open and closure of curly brackets {{}} Please, try to follow the steps described to replicate the same solution and check it's a working solution with no changes of formulae after having copied the column. Of course, depth…

Hi @sh0716_lee , It should work. Does it return any errors? Is there anything in red color? If no errors are being thrown, then it might be due to having applied an incorrect depth level. In order to be sure, add a new formula column just with this formula: depth After that, ensure that n2 formula has depth = (the…

Hi @sh0716_lee , If I'm understanding it correctly, you would like to set a column like the one titled Formula in the following picture: The n3 column in the screenshot is your workload number custom field. Just follow these steps in order to achieve the resulting Formula column: * Add a column of type Formula, change its…

Just to complement @Aditya Sastry answer, this is the link to Script Runner's documentation about the Issue Picker field.

Jira Cloud has recently been boosted with Automation natively. So, many use cases may fit better in a manually triggered rule than in a global looping transition. The automation rule may be executed by entering the Rule executions menu > <your automation rule>.

@William Sippl Nothing new under the sun. At least in regard to achieving that natively. If you count with Script Runner, then you'll be able to get the sencond filter like this: issueFunction in epicsOf("filter='My issue keys'") Provided you have a saved filter with that name (My issue keys), which would look like this:…

Have just tried this query both in Cloud and Server 8.6.1 and the NOT and ! syntax do not work with text. Should have tried it before posting this answer. Have just unaccepted this answer. Please, refer to the new answer marked as accepted.

Edited: The NOT keyword doesn't work with text: NOT text ~ apple Neither this other equivalent syntax: !text ~ apple

Hi @bschmi Blankspaces are not stored at all in the Lucene index, so they cannot be considered in any ways. Too common words, like prepositions, are not stored in the index either. Combinations of letters plus numbers is known to cause issues: https://jira.atlassian.com/browse/JRASERVER-31882 Just for curiosity, does this…

Thanks @Kristian Walker _Adaptavist_ !

Hi @prabakar_m The first query requires the help of a third party app like ScriptRunner for Jira Cloud, thanks to the hasLinks() function: issueFunction in hasLinks("is blocked by") AND type = Sub-task The count of linked issues for each subtask is even trickier to obtain on Cloud. Maybe you can export to csv using the…

Hi @Kaushik Patel , If I'm understanding it correctly, the following query would return the subtasks you need to transition: type = Sub-task AND status in (abc, xyz) AND issueFunction in subtasksOf("type=Task AND status in (MNO, EFG)") Should you need to include status names with a blankspace, enclose them in single quotes…

Hi @prabakar_m , As Thomas suggested, the paretEpic function is what you need here. Best regards

Hi Timothy, The Control Chart can be set to obtain throughput, cycletime and lead time, depending on the selection of columns you choose in its configuration settings. If you create Quick Filters in your kanban board, those filters would be available for narrowing the group of issues used in the calculations and in the…

@Andy - PTC RedundantHaha, yeah, you have to feel the pain before being able to understand this tip. 😆

Hi @Aaron Lemley , Try adding this syntax at the end of your query: ...AND NOT paretEpic = EPIC-101 ...where EPIC-101 would be the issue key of the epic you want to exclude, together with its stories. Hope it helps.

Hi @Jeremy_Johnson, Issues resolved within the last 30 days: resolved > -30d Issues resolved since the 00:00 hours of the first day of last month: resolved > startOfMonth(-1) Hope it helps.

Hi maksya, I would suggest using a board for that purpose (either a Kanban or a Scrum one), so that you can check its Cumulative Flow Diagram report, which shows the number of issues in each selected columns over time. For said report to count with the tools you need, follow these steps: * (if PROJ lacks a board) Create a…

Hi Shriya, Analyzing whether or not a specific custom field is actually being used in a Jira instance is a really interesting topic which could lead to a really extensive answer. Deleting unnecessary custom fields is a maintenance task every Jira Administrator should eventually approach. I'll add just some tips on this…

By the way, another Scripted Field which code is available here could retrieve the number of weekdays since the Sprint field was last updated. It would require just to update "Custom Field Name" with "Sprint".

Hi Wendy, If I'm understanding you correctly, you'd like to count with a field that displayed the last sprint an issue was in, instead of showing all sprints where the issue had ever been, which is the native Sprint field behaviour. Natively, there's no way to show just the last sprint into a column or field. With…

Well done, edwin! This is a correct answer. Just for mere syntax simplicity, I'd use this last part instead: ...AND NOT status changed after -5d which is just a little bit shorter. But your answer is absolutely correct and will work perfectly. Regards

Hi Evan, JQL is based on Lucene, and the Search index does not store any special characters, such as a pipe "|" character: The index only keeps text and numbers. That said, I'm afraid there are no direct ways to get the issues you want just by using Jira Cloud native JQL functions. ScriptRunner for Jira Cloud counts with a…

Hi Tiago, Unfortunately, parentEpic function does not support a subquery as a parameter. Sample queries that could be of help in a workaround solution include: * parentEpic in (EPIC-1, EPIC-2, EPIC-3) * parentEpic in issueHistory() * parentEpic in votedIssues() * parentEpic in watchedIssues() A several-steps solution would…