Andy Heinzer Atlassian Team

Sprints are independent of boards. However boards will restrict what issues appear on them due to their board filter. Hence when you close a sprint listed on board A, that same sprint is also closed on board B. But since you can't see the issues on board B from board A, there is no means indicate to Jira where to place…

Sorry, but I am not certain I understand what steps you are taking to add a Jira issue to a version. The process you described does not sound familiar to me. Perhaps this is something new I don't know about yet, but I don't recall being able to drag issues into a version in order to set the fixVersion field for that issue.…

Kanban boards have an addition subfilter JQL that you can add to it. See Configuring Filters: (Kanban only) Adding a sub-filter for more details. This subfilter is used to limit which issues appear on the board itself. This is helpful because the issues themselves can still be shown in the related reports for that board,…

Hi Sheryl, I understand that you are looking to be able to make a single REST call when closing the issue that will allow you tell Jira Software (Agile) where to place those incomplete issues in the sprint. As you noted this does not appear to be possible within the REST API at this time, but I agree that this seems like a…

Hi Vassili, Is this a Jira Cloud instance? If so, it might be best to create a support request for this problem over in https://getsupport.atlassian.com If this is a Jira Server instance, you can still create a support request there, provided that you are a named contact on a non-starter license, but our support team will…

Hi @John Xolobo So far, I have not been able to reproduce this problem. Could you let me know more about your environment? Are you also using a Linux OS, like Tom initially reported on this thread? Could you let me know what specific versions of Firefox and Chrome you are using? Have you tried to use the Private browsing…

To the best of my knowledge, this connection pool data seen in the graph on that page is not actually being stored anywhere else within Jira, such as the database or other log files. If this is something you want to log and track, you might want to take a closer look at a plugin such as the JavaMelody monitoring plugin.…

From your screenshot I can see that someone in your Jira instance created a resolution called 'Unresolved'. While this might be ok in some cases, this can cause confusion because Jira will tend to show issues that do not have any resolution value as 'Unresolved' note the italics. There is a pretty comprehensive KB on how…

Your JQL query is not actually sorting the results at all. If you want to do that, you will likely need to add in the 'ORDER BY' clause, select a field to sort by, and then a direction (ascending or descending). If the JQL was in Jira it would look something like this: assignee=admin AND created>=2018-01-01 AND…

Hi @Aarti Parikh I have had a similar problem before when trying to setup a gmail account within my Jira instance. In my case I did actually have 2-step authentication and I also had to enable the 'less secure apps' option. But even after I did this, I still found that my instance would create this kind of error at first.…

Hi, This behavior is actually expected. The 'request type' field is not something that is expected to be set when creating a ticket this way. Whereas when you create an issue via the customer portal, the user has to select the request type first. But there still is a way you can get Jira to automatically set a request type…

Jira data center nodes need to access a shared location for the shared Jira home path. For windows you should be able to follow the steps in Share a Folder or Drive to be able to do this. There are other possible solutions here, but specifically for windows, this is one way you could create a shared path that the other…

I have not seen this happen before. However if I had to guess it seems like that the initial estimate for the amount of data to be imported might be inaccurate vs the actual data being imported. However I have not seen any other reports of this specific problem before. So I am curious to learn more about your instance and…

Hi Mike, Sorry for the delay in response, but from what you have stated so far, that makes sense. If Jira is being started by another user like root, this system thread limitation can behave differently for the root user versus other user accounts. We would recommend that you have a separate user account specifically to…

Awesome, thanks for letting us know that this helped resolve this!

Hi @Damian Payne Thanks for posting back with the solution you found. I am not familiar with this specific Tomcat property, but I was able to find this documented in their documentation on https://tomcat.apache.org/tomcat-8.5-doc/config/systemprops.html In that document, it mentions that using that parameter could expose…

Hi @Grzegorz Koper, Thanks for the additional suggestion here. We do appreciate the added input here. Hopefully the original poster, and other users, will find these replies helpful. On a side note, please review the Atlassian Community guidelines for marketplace vendors. When suggesting your own add-on (app) on Community,…

Hi @Dermot Kelly Sorry to hear about this error. However this appears to be a known bug. Please see https://jira.atlassian.com/browse/CRUC-7410 for more details. While there does not appear to be a work-around listed for this at the moment, I would recommend watching that bug ticket. Should this be fixed in an updated…

Given this error it makes it appear that Fisheye still believes there is an existing entry for this jira in regards to the application link. This entry might be in the database, but it might also be getting generated by a the config.xml file on start up. If trying to remove this from both applications did not work, then…

What version of Jira are you using? There was a known bug about this health check throwing false positives for this specific health check a few versions back as I recall. If that doesn't help, there is a KB on this kind of error in Health Check: Thread Limit. That specific KB talks about ways to fix this problem. Also what…

Hi Thian, When you have this chart setup to look at more than 30 days worth of data, this chart changes from using a linear scale for days into using a cube-root scale in regards to the vertical axis that measures days. I would recommend checking out the documentation in regards to this in Viewing the Control Chart:…

In regards to number two, you could do this with Scriptrunner. It does allow you to use some additional JQL functions that can look at parent issues values or subtask issues values in regards to which issues to return. The native JQL in Jira can't really look at specific values on related issues like this. But if you had…

There is a known bug ticket for this problem in https://jira.atlassian.com/browse/JRASERVER-66069 It's not technically a bug in Jira, but we have found that some specific Linux OS instances that host Jira can have this specific problem when specific fonts are not installed. There is a work-around listed on that page that…

Are you using Jira Cloud? Is this by chance an Kanban board? Kanban boards have not always had this feature to show epics in the side view like Scrum boards have in Jira Software. But even in the new layout, you should still be able to configure Jira Cloud Kanban boards (or Jira Server 7.4.x kanban boards) to show the Epic…

If you're using Jira Cloud, you don't have a means to access the SQL database at all. However if you are using Jira Server, it might be possible to hack at the database to adjust this as described in the KB How to reset the project counter after moving issues.

By default Jira has a connection pool value of 20, so that would seem to fit in with the 18 separate connections you are seeing. You can try to Tune the connection pool settings, but just be aware that incorrectly adjusting this can negatively effect performance in Jira very easily. As for the clustered SQL support, that's…

Hi Jan, Thanks for further explaining what you are looking for here. I found a past feature request that I believe is similar to your request in https://jira.atlassian.com/browse/JSWCLOUD-6945 In that case, the user wanted to see the epic just like any other issue type in the backlog. You can see in the comments there that…

We have a number of Feature Requests to be able to report on the time that Issues were in a particular status while the were opened, however many are quite old and have not had a lot of feedback or input on them: * https://jira.atlassian.com/browse/JRACLOUD-41234 * https://jira.atlassian.com/browse/JRACLOUD-60841 *…

You can certainly sort/view issues on a backlog by their epic. There is some documentation that helps explain how to use epics with the boards such as: Working with Epics. You will notice that Scrum boards, (and more recent versions of Kanban boards) will have both a "Versions" and "Epics" tab on the left side of the board…

Sorry for the delay @Krystian Szczęsny I suspect that perhaps the group that grants login rights might have also existed in the other directory. And even if you migrated all the users, this doesn't necessary migrate all the groups that grant permissions in Jira. And since Jira does not aggregate permissions across user…