Ignacio Pulgar Expert

Try this query: (project in (11006, 11004, 10402, 11005, 13007, 10900, 10314, 10327, 10315, 11003, 10326, 11007, 11002, 11001, 10401, 15100, 10311) OR (project = 11009 AND component = "Cloud Infra")) AND "Scrum Team" = "AA Team" ORDER BY Rank ASC

Do you count with ScriptRunner? Is it a Cloud instance? Or is it a Server one?

!(type = sub-task AND status = "To Do")

I don't like to answer questions which response is summarized as "you can not do that", but this time I'll do. On Jira Server, that cannot be achieved natively without the help of a plugin. On Jira Cloud, there's a convenient native function named parentEpic() which also returns subtasks, but I'm afraid it is not available…

The red cross icon is displayed while the query cannot be executed without throwing an error, therefore not returning any issues. This usually occurs when there's a syntax error as well as while you are typing a correct JQL, but you have not finished typing it yet.

On Cloud, ScriptRunner's issufunction does not work directly in the Issue Navigator, as it requires to use the Enhanced Search section instead. However, filters created and saved through in the Enhanced Search can be used, in example, to feed gadgets. That said, I think it's worth trying to save a filter from the enhanced…

Then you don't have ScriptRunner addon installed in your Jira instance. You may consider buying it (it is a worthy one)...

Is it a Jira Cloud instance? Or a Server one?

ScriptRunner for Jira is a third party addon which belongs to Adaptavist, and needs to be acquired independently from Jira, but it is embeded within it, as it an extension of Jira capabilities. You've mentioned Scripted Fields, which is a type of custom field provided by ScriptRunner, so I'm assuming your Jira instance…

There's no native way to do so, but provided you count with ScriptRunner, you'll probably be able to set a Scripted Listener which listens to Issue Edited events in order to register the info you need to be able to query.

That's only doable with the help of an addon. If you count with ScriptRunner, then your query would be: issueFunction in linkedIssuesOf("type=Bug AND creator=currentUser()") Save that query as a filter so that you can use it to feed a pie chart.

Sorry to hear that...

Please, have a look at this page: https://confluence.atlassian.com/adminjiraserver073/associating-screen-and-issue-operation-mappings-with-an-issue-type-861253453.html Besides, the diagram in this other page is quite good for understanding schemes:…

Besides the previous correct answers, you may also want to create a Project Category named ABCD and add all ABCD projects into it. That way you'd be able to query issues from all ABCD projects at once with this simple JQL: category = ABCD

I'd ask eazyBI Support about this issue. They may provide you with some indications to minimize the required time.

More info needs to be collected from the logs in order to get a clue. Have a look at the last section of this KB article: https://confluence.atlassian.com/jirakb/notifications-troubleshooting-203394737.html

Now you just need to set that Issue Type Screen Scheme on each of your projects: * Enter the project configuration section. * Click on the Issue Type Screen Scheme currently set. * Click on the button on the rop-right corner and select 'Use a different Issue Type Screen Scheme and set the one you've already created. Repeat…

This is doable natively, but it requires a really large JQL query. For the query to be dynamic, with no need to update the dates, you may use something like this: (created >= startOfMonth(6h) AND created <= startOfMonth(15h)) OR (created >= startOfMonth(30h) AND created <= startOfMonth(39h)) OR (created >=…

Without the help of an addon, it would only be possible to adopt a procedure to produce the desired result. If users in your organisation added a label to all issues in a sprint on starting it -through a bulk change operation- then you would be able to retrieve them at a later stage.

That's right. Have you tried the Include Page Macro?

Try this query: attachments is not EMPTY and type = Story

If it is a Jira Cloud instance, it may have something to do with this: https://confluence.atlassian.com/cloud/blog/2018/06/say-goodbye-to-usernames-in-atlassian-cloud So, you may change the authentication method from basic to anything else (I think Oauth is the most recommended way).

Oh! Nice one! 😅

Another macro that may be useful for these purposes is the Include Page Macro.

You may do so by using the following macros: * Excerpt Macro * Excerpt Include Macro Hope it helps.

Natively, you may write a JQL by providing the parent's issue key like this: key = JSWSERVER-8942 OR parent = JSWSERVER-8942 If your instance counts with ScriptRunner, then you'll be able to use one of its JQL functions to avoid having to provide an issue key. Please, let us know if that's the case, so that we can assist…

Yes, you need to be a member of the 'site-administrators' group (or site-admins, not sure at this moment of the exact literal).

Why don't you just set the Assignable User permission to that of the group picker custom field in the project's permission scheme, removing that permission from anyone else?

It usually depends on the requirements, but provided you're on Cloud, I'd recommend using just one workflow, because of this existing bug: https://jira.atlassian.com/browse/JRACLOUD-67800 That bug basically prevents workflow properties to work properly in projects that count with more than just one workflow set. So, I'd…

ie: You may override the functionality of header's onClick() events so that they behave in a different manner, or add a button that ordered the displayed issues in a given manner.