Comments
-
It sounds like you might be seeing the bug https://jira.atlassian.com/browse/JRASERVER-62386 However this bug documents how JIRA can change to use the project id number in the JQL filter itself. It doesn't actually change the results of that filter. So that likely explains how JIRA is using that filter. But it doesn't…
-
https://answers.atlassian.com/questions/166537 has some good explanations on how you can search JIRA for issues that have links. JIRA natively does not have a function to do this. But there are several plugins that can better help with this kind of functionality
-
They have added some sample exam questions for the ACP-100 : JIRA Administration: http://atlassian.articulate-online.com/8679133671
-
I'd take a look at the startup logs for JIRA. It's not uncommon to see in the logs that JIRA can timeout trying to render the activity stream on large environments with lots of issues, when this happens a number of times in a row, the stream can actually become banned and then JIRA doesn't try to load it again for a full…
-
This is by design within JIRA. I would recommend that you vote on the open suggestion over at https://jira.atlassian.com/browse/JRA-34268 in order to improve this within JIRA. I agree that the wording can be misleading, but this is the current behavior within JIRA.
-
According to the Oracle JVM Tuning guide: https://docs.oracle.com/cd/E40972_01/doc.70/e40973/cnf_jvmgc.htm#autoId2 setting the xms to be the same as the xmx will prevent pauses caused by heap expansion. In turn it can help prevent performance issues within JIRA while waiting for JAVA to deal with memory allocation changes.
-
There was a known bug where trying to do these kind of mentions would fail. Please see https://jira.atlassian.com/browse/JRA-45836 If your JIRA site URL begins the domain with the same letter, and you're using a JIRA server 7 version before 7.1.8, then it is likely that this bug is affecting you. An upgrade to JIRA Core…
-
There are known limitations with trying to jump this many versions at once. We first saw this with any JIRA Agile 6.3.xx.x versions that tried to upgrade to JIRA Software 7.1.x versions.…