Ignacio Pulgar Expert

Hi Nelson, There are no native ways of getting the result you seek by native means. Some third party apps from the Atlassian Marketplace might help, depending on the purpose of the query. If the number of Days in Advance could be calculated solely based on the current information of other field values form the very same…

Hi Markus, Here we have answers to your questions: * JQL queries will either retrieve an issue or not. They will never return an issue more than once, no matter the query. * If a static date is provided without a time, the time will default to 00:00 hours. You may also add a specific hour to your date like this:…

Olga's approach is the correct way to go here. You will also need a similar filter but for -60d, similarly with a daily subscription. For nothing to be sent when no issues are returned by the query, ensure you don't select the checkbox Email this filter, even if there are no issues found (already unselected by default).

+1'ed. https://scriptrunner.adaptavist.com/latest/jira/jql-functions.html#_datecompare

Hi Andrew, Unfortunately, there are no native ways to get what you need: an app or script would be required. As a workaround, you may: * Go to the issue navigator and save as a filter the query you would like to order by labels. * Ensure the Issue Key and the Labels fields are being shown in your selected columns. * Export…

Hi Lauren, The following query retrieves the specified epics: key in (EPIC-1, EPIC-2, EPIC-3) This other one gets the issues that belong to any of the specified epics: "Epic Link" in (EPIC-1, EPIC-2, EPIC-3) As your Jira instance is on the Cloud, you may get the list of epics, plus issues within any of those epics, as well…

May you check if the JSU post function is positioned after the reindex post-function? (it should be before instead)

Maybe the index is corrupted. You may want to eliminate the index and build it again from scratch: * Shutdown JIRA * Delete all the contents from the following folder:$JIRA_HOME\caches\indexes * Restart JIRA * Perform a full re-index Hope it helps.

Reviewing the Search syntax for text fields, it is said: "The index only keeps text and numbers". That's why "blue" and ".blue/" return the very same issues. Unless there are other words that you can use for narrowing the search (ie: www, http, https...) for building a proximity search, it is unlikely you may get what you…

Hi jocortals, The field name you need is named timespent. Hope it helps.

Hi Hector, May you try if the following query makes any difference? text ~ blue AND NOT text ~ "\".blue/\""

Hi Jason. I'm afraid there's no JQL way in Jira Server to get the subtasks of issues that belong to the specified epic without the help of a plugin. Of course, there would be ways for getting them through SQL, by querying directly against the database, but that's usually considered a bad practice...

Hi tahay, I'm curious, what's the purpose of asking for IDs that might not exist? Regards

You need to count with ScriptRunner addon installed in your Jira instance for being able to use issueFunction.

Hi Paula, There are several ways a label can be set to be added to every new ticket. I'd check the following sources, ordered by the estimated likelihood of being the case: * Service Desk Automation Rules * A post-function in the Create transition of the workflow(s) * If you count with ScriptRunner, then look for Script…

https://confluence.atlassian.com/jirasoftwarecloud/customizing-cards-764478020.html#Customizingcards-fieldsAddingfieldstocards

For this use case, maybe it's better setting 10 Quick Filters (1 per component) instead of 10 swimlanes. It may also be helpful including the Component field in the card layout. That way you will easily detect issues belonging to several components with no need for selecting them.

Hi Niklas, The board swimlanes have been designed to work this way: For each issue returned by the board's filter, the top-most JQL query in your swimlanes definition will be executed. If the issue would be returned by that JQL, then that issue will be assigned to that swimlane and the next issue will be processed.…

Hi @MCjiraLearner , An Automation could solve your need. The idea would be flagging the main issue once the first of both linked issues had been solved, in order to keep track of the action that needs to be executed. In the sample Automation configuration below, we have used the field Labels for this purpose: Please note:…

Hi Geoff, Unfortunately, cron expressions do not natively support the "every two weeks" time period. There are workarounds that might work for certain scenarios, but I'm afraid none of them would work for filter subscriptions. However, there are very convenient and free Cron Expression Generators online that might help you…

Hi BhanyPrakash, You may get all issues which belong to an open sprint by executing the following query: Sprint in openSprints() You may also filter by project or add the same filter used in a board. Save the filter with a descriptive name, ie: Issues in open sprints. Create a dashboard and add either a Pie Chart or an…

Glad to help! :) Regards

Hi Anas, Unfortunately, there's no native JQL function to get issues that were not completed in a sprint and later added to a new one. Assuming you were only interested in issues that belonged to a sprint at the very same moment of the sprint closure, and not in issues removed from a sprint after it had already started,…

Hi Jyoti, There's a bug that might be affecting you: https://jira.atlassian.com/browse/JSWSERVER-13996 The workflow set for Defect issue type might count with a post-function on its Create transition for auto-transitioning it on creation. Is that the case? Regards

Hi @Andy - PTC Redundant , It took me a little bit to understand this tip too. @Derek Fields _RightStar_is referring to the creation of screens that are usually added to transitions just to edit just one field, like Resolution, Assignee or Comment, which are very frequent cases. That's useful when there are multiple Jira…

@Esther StromPlease, note there's currently a bug with global looping transitions on Cloud instances with the new issue view: JRACLOUD-72667. @__ Jimi Wikman& @Luiz Carlos Maia Junior The simplest use case I can think of would be restricting the edition of the Priority field so that only users in Administrators project…

Thanks @Yolanda Sánchez ! @Antoine BerryIndeed! If only it were more visible... That's why I recently created this feature request: https://jira.atlassian.com/browse/JRACLOUD-72730 Please, vote for it to make Jira an even better product! :)

Oh, I see! I was about to suggest contacting Atlassian Support, but fortunately anyone else already did (I'll paste the known issue here just for other users convenience): https://jira.atlassian.com/plugins/servlet/mobile#issue/JSWSERVER-13996 The bug occurs on issue creation, just with issues which automatically…

Is your custom Bug issuetype of subtask sub-type? If so, that's the cause. Story Points on subtasks are not included in the Burndown Chart. (Only Story Points on parent tasks are included.) https://confluence.atlassian.com/jirasoftwarecloud/burndown-chart-777002653.html

Jira Software Server or Cloud? If Server, what version?