Ignacio Pulgar Expert

Hi Oana, That's the expected behaviour, as filter subscriptions' JQL queries are internally executed once per each subscribed user, so that it returns the issue results that they would have obtained by executing the same JQL query individually in the Issue Navigator. Processing the query on a per user basis is needed in…

I would need some info to help you further: * Did you follow this step by step guide, adapting it to your custom field? * May you paste here your script? * Did you map the behaviour to the correct project(s) and/or issue type(s), and performed your tests accordingly?

Awesome! Glad it lead you to the workaround :) Regards

That's really strange. I'd contact Atlassian Support for this: https://support.atlassian.com/contact/#/ Please, update this question if you find out what happened, so that other users experiencing the same symptoms can fix the issue faster. Best regards.

That's a known issue: https://jira.atlassian.com/browse/JRACLOUD-65048

Script Runner for Jira Cloud can achieve that through enhanced search with a query like this: issueFunction in subtasksOf("type = <ISSUE TYPE>") Note that this kind of search is executed outside JIRA's built-in Issue Navigator. There's a rough workaround for achieving this with no need of plugins, but it requires several…

Alexey's answer is a perfect response to the literal asked question. However, the most correct approach for receiving notifications about all issues in a specific project wouldn't be adding those users automatically as watchers to every issue. The recommended solution is achieveable with no addons, by following these…

You're welcome Carlos! :)

You're welcome! If you'd like to go back to the issue navigator, you can also do it with a shortcut g+i. Regards!

Press the shortcut g+p (go project) from the issue navigator, and it will direct you to the current project (the last one visited by you).

Let me recommend Time Reports for Jira. Besides the screenshots shown there, it also allows grouping by worklog author.

Alright, then that's a good way of getting a rough indicator for that purpose. ;) Best regards

Exactly! If you would like to promote efficiency, I would try a plugin for introducing gamification into JIRA, like Jiraffe. Giving points and badges is known to be a good way to improve participation and quality of contributions. Please, do not use it to try to measure real effort, but just as a way that might help people…

Please note that your query doesn't target the Assignee field at all. Literally, your query will return any issues that had ever been transitioned to the status "In Progress" by the user developer1. If the underlying workflows had all transitions that target "In Progress" with a condition like "only the assignee can…

Yes, you can do so by editing the board filter shares, if you are the owner of that filter. Find the filter which populates the board by going to Confligure > Board and, in the General section you will find the board's filter. After that, delete any undesired shares by clicking on the bin icon:…

By the way, you may also try setting some days into the endOfDay() function like this: "Release Date" >= startOfDay() AND "Release Date" <= endOfDay(30d) The query above would return issues which Release Date had been set to today or within the next 30 days after today.

Then I'd say the release dates are future ones, from the start of tomorrow in advance. If that's the case, returning no issues is the correct and expected result. Just to test it, may you try creating a dummy issue in a dummy project, setting today as its release date, and perform a similar query?

Hi Bruno, Displaying such a calculation within Jira is only possible with the help of a plugin, like a calculated field from Jira Misc Custom Fields or a scripted field from ScriptRunner. That said, I'm a little bit sceptical about "Original Estimate / Time Spent" being a valid metric for measuring people efficiency.…

It's a typo. Change "=<" to "<=".

Xray is only available for JIRA Server and it is not possible to have it installed on a JIRA Cloud instance.

May you check that: * the board's filter ends with "...ORDER BY Rank ASC" * and that the quick filter doesn't include the ORDER BY clause? Having the issues not ordered by Rank is known to cause problems with the drag & drop functionality. If that's not the cause, I'd suggest to open a ticket with Atlassian Support.

Jira Query Language doesn't support that kind of text search natively. However, ScriptRunner provides a search function that supports regular expressions, so maybe the following query returns all issues from FOO project with a description of less than 10 characters: issueFunction in issueFieldMatch("project = FOO",…

Hi Carlos, The Issue Type field's description is currently not displayed in the Create Issue Screen. Maybe that's because its description would vary depending on the specific issue type actually selected. Once an issue type had been selected, that issue type's description will be displayed on hovering the mouse cursor over…

Awesome! Glad you could finally fix it! Regards

That said, NULL values simply do not have a row in the CUSTOMFIELDVALUE table.

Every issue has an entry in the JIRAISSUE table with its own numeric id. Likewise, every custom field is represented as a row in the CUSTOMFIELD table with its id. There's an intermediate table between both of those tables named CUSTOMFIELDVALUE, each of which rows contains one issue id, one custom field id, and the stored…

If that's the case, make sure you load the html elements before referencing them in your script, as shown here: https://stackoverflow.com/questions/18239430/cannot-set-property-innerhtml-of-null

Do you have any javascript custom code? Maybe in JIRA's Announcement Banner?

Then I'd suggest to include the expected date ranges in the Sprint Names.

The JQL by Alexey is the one you need. It was a matter of parenthesis; all you put after an OR do not take into account previous clauses, so it usually requires to carefully enclose something between parenthesis.