Identifying a existing Jira project

[Suma Pralhad Kustagi]

Hi All,

     How to identify if the existing project is a scrum or Kanban project in Jira server  and project does not have any boards associated.

Regards,
Suma

[Chag]

you should also upgrade the hardware. With the number of issues and what not you should upgrade...

[Norman Abramovitz]

https://confluence.atlassian.com/display/JIRA/JIRA+Requirements#JIRARequirements-3.ApplicationServer Since you are probably running 64 bit you should experiment with increasing your VM memory. Running with 1G is definitely too small. You should be able to memory usage under admin/system screen.

[Luciano Fagundes]

Conor, troubleshoot performance issues is always a challenge since it envolves multiple variables. I recommend to take a look on the following documentation which provide some guidelines to troubleshoot this sort of issue.

https://confluence.atlassian.com/display/JIRAKB/Troubleshooting+Performance+Problems

Taking thread/heap dumps and enabling the garbage collector logs always provide some pointers of what might be wrong with your instance.

Hope it helps!

Luciano Fagundes

Atlassian Support Engineer

[Norman Abramovitz]

Hi,

JIRA does remember the last search, so if users select "current search" instead of "Search for issues"  this would avoid the full search for the most part.   We also added the "Favorite Filters" gadget to the dashboard, so users can avoid pulling down the menu to click on their saved searches(filters). 

I am fairly confident that MaxPermSize is too small, but I usually need to see the JIRA memory usage to make an educated guess since memory usage depends on many things.    This also means that most likely you should also add memory to your physical machine.   With JIRA and MySQL on the same machine you should be memory starved.with only 4GB.

https://confluence.atlassian.com/display/JIRA/Increasing+JIRA+Memory

Click on the diagnosis link to see the information I am pointing you to.

[Norman Abramovitz]

JIRA released 6.3.7 recently

[Conor McCooey]

John and Norman, thank you kindly for your responses. I plan to upgrade our instance to JIRA 6.3.6 this weekend to hopefully see some improvements.

The default behaviour "Search for issues" to bring up the Issue Navigator is a real annoyance for our user base. It first loads all the issues in our instance, before allowing users to enter the JQL query they actually want to run. Everyone complains about it. Can this be changed?

To clarify, do you not believe the following VM setttings are enough for a JIRA instance of our size -

MaxPermSize=1024m -Xms2048m -Xmx2048m

And finally, could reducing the default user session limit down from 5hrs help with performance?

Many thanks,

Conor

[Norman Abramovitz]

There has been some performance issues fixed recently.  I would try a latest build to see if your problem is resolved.

https://jira.atlassian.com/browse/JRA-36368