Ignacio Pulgar Expert

By the way, what's the JQL shown after clicking on the number 125 from your screenshot?

I think Atlassian looks every suggestion sent to them, especially those with many votes. I'd bet they have had many sessions around those issues, but some implementations just might either not be feasible or have a huge impact on other features and/or integrations with other apps. The more you know an app, the more you'll…

You're welcome, Luis! Once you fix the issue, please, update this question with the answer so that other users with the same problem can take advantage of your research. Best regards!

Does the automatic assignment set the component lead of the selected component? Is it a feasible solution to remove 'Component Lead' as the value for Default Assignee option?

I'd recommend opening a ticket with Atlassian Support with a description of the issue (and maybe a link to this question): https://support.atlassian.com/contact/#/ In the meantime, may you run the Integrity Checker and see if it returns any errors? <your Jira URL>/secure/admin/IntegrityChecker!default.jspa

That's really weird... May you reindex project AAAA and refresh the dashboard page?

May you possibly attach a screenshot of the gadget so that we can see the wrong results?

Let me give an example. I've saved a filter which returns just 1 issue, and that issue has 2 labels: 'a' and 'b'. I've set a two dimensional gadget with Status and Labels using that filter, and this is the counter-intuitive result: Is that a similar case?

Hi Luis, Maybe the other axis is based on a field that accepts multiple values (ie: components, labels...) and there are some issues with several values being retrieved by your filter. Because of that, the values are being counted as many times as they are true for that Status and multivalued field, therefore showing…

Maybe the Components field is being given a value, and that component has a component lead set to be the default assignee?

Just for the record, please, kindly note that Alexey might be willing to help you, solely based on his own decision, as he does not have any obligations to solve, or even to answer to this question. Community Champions contribute here just for fun. So, we are in fact asking him for a favor :) Best regards

Hi Carlos, Good news! You'll be able to achieve what you want. Fortunately, the Order By clause doesn't order the Status field alphabetically. You can decide the order of statuses from: <your Jira URL>/secure/admin/ViewStatuses.jspa Just click on the up/down arrows to order the statuses as per your needs: After that,…

Hi Akhil, Provided that dateCompare compares just dates from the very same issue, groovy code is required. Maybe @Alexey Matveev can help you further, as he is a distinguished Champion with widely proven scripting expertise. Regards

Glad to help! Mind that you can filter that further for getting only issues where the user who had logged work belongs to a certain group, with a query like: workratio > 100 AND worklogAuthor IN membersOf("jira-administrators")

The most straight-forward JQL for excluding an epic from the filter would be: type = Epic AND key not in (<epic issue key>) Where <epic issue key> could be, in example XYZ-258. Note that you could easily exclude more than one epic by adding their issue keys separated by commas, ie: type = Epic AND key not in (XYZ-258,…

Natively, you can get all issues where the time spent is higher than the original estimate with this JQL: workratio > 100 By showing the assignee in the Issue Navigator, you will get the info you need. You might want to save that query as a filter in order to feed a Pie Chart by Assignee in a convenient dashboard for…

Hi Akhil, Do you have ScriptRunner plugin available on your Jira instance? This one would avoid the necessity for coding, as it provides many convenient JQL functions. By the way, speaking of Issue Links, we better speak of outward and inward links, rather than parent-child relationship, unless you are specifically…

Hi levan, What do you mean with 'SR owner(name)'? I assume you want to filter issues with an active Jira user as its value. Such Jira built-in fields can be queried like in the following examples (looking for 'Bob' issues): assignee = bob reporter = bob creator = bob A similar approach can be used with User Picker custom…

Many good tips for Jira Administrators have already been posted here and don't want to repeat variations of those tips. Instead, I will focus on giving some tips to Jira Software admins about features that were not available to Jira Core admins, or that despite of being Core stuff it would be advisable to have into account…

The best answer to this question has been covered by a dedicated article by Rachel Wright: https://www.jirastrategy.com/content/who-does-what-in-jira

Really agree with all those 6 points.

That's a fantastic idea!

Unfortunately, not natively.

By the way, note that components need to be created in a per project basis before they are available in JQL. The creation of components in a project requires Administer Projects permission, which is usually granted to users with the Administrators project role (check if that's the case in the project's permission scheme).

Components are certainly queryable by JQL. Try the following query: component is EMPTY Does it return any results? Now try: component is not EMPTY What about the results of this one? 

My first thought on reading the error is that there might be some corrupted data in the database, having a NULL where it is expected to have a value and it's colliding with a table constraint. After a quick research, I read that empty strings are treated as a NULL value by Oracle DBMS, so that might have something to do…

May you check if you can actually enter the issue detail view of issues created by others? If so, may you try entering the issue key (ie: FOO-57) into the issue field that appears on clicking on Link option?

That's not doable without the help of a plugin. On Cloud, you also count with the function parentEpic() which might be useful in some cases, but it doesn't resolve your needs here. With ScriptRunner, the filter would be: issueFunction in issuesInEpics("Objective = 'Objective A'") Hope it helps.

Also note that Scrum backlogs do not show issues of type sub-task.

Another factor that might be causing discrepancies in the issue count between boards is that Scrum's backlog won't show any issues which status is mapped to the last (most-right) column.