When I get into the Issue Navigator for a project I see the issues sort according to Priority by default. We don't really use Priority in our projects, so it's annoying to have to select a new field (which I can't scroll to, btw) and then re-select the ordering, and THEN, if I'm lucky, I don't have to change the filter, otherwise the view defaults to sorting by Priority.
I can't find any documentation on how to configure this setting. I want to be able to have the issues sort by Key, descending, when I open the Issue Navigator. Anyone know if there's a way to make that happen? Thanks!
I am experiencing the same problem ever since I upgraded to JIRA 6. However, in my case I have determined that the behavior is caused whenever I have Confluence opened in another tab. If I close out all my Confluence tabs, the behavior goes back to normal. There are some suggested workarounds mentioned in the accepted answer to this question, but I haven't tried them.
Hi Kevin,
I was able to resolve a very similar problem, though the answer was not posted for various reasons.
However this is the link that helped me.
https://confluence.atlassian.com/display/CONFKB/Logging+into+Another+Atlassian+Application+Logs+Me+Out+of+Confluence
Basically what is occuring is this. Your Confluence and JIRA installations share the same Base URL or path but connect through different ports. The cookie that saves your login data does not save port information. This link will walk you through how to change the stored SESSIONID for both applications. When you log into JIRA it creates a cookie. Then when you login to Confluence it is over writing that cookie and JIRA thinks you logged out. By changing the session ID for each application this will no longer occur. The other option would be to change the path for each application. I am not sure of any specifics of your setup but this is what solved my issue.
Cheers,
Rich
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Awesome! Resolution Option 2 seems to have resolved it for me (and no restart required). Thanks for posting, Rich!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
https://confluence.atlassian.com/display/CONFKB/Logging+into+Another+Atlassian+Application+Logs+Me+Out+of+Confluence
Answered my specific problem
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Richard,
You can refer to this document to fix your issue:
https://confluence.atlassian.com/display/JIRA/Configuring+Secure+Administrator+Sessions
Best Regards
Steven
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have read the article and had found that information previously. I prefer to have the secure administrator session enabled, but it prompts for a password well before 10 minutes.
I have worked around this by disabling the feature during large upgrades but would prefer to have it active. Some plugins would show errors because I would be prompted for admin credentials mid upgrade. I hope this is corrected in future versions of JIRA.
Thank you for your help.
Rich
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.