Andriy Yakovlev [Atlassian] Atlassian Team

Hey @MadelineBarr Good question. We don't have a specific version yet, it's WIP, it should be something 9.x (where 2< x < 5). Regarding the timeline it's end of Q3, so customers have a smooth upgrade from previous LTS 8.13.x. Hope this helps :) 

Hey David, Advanced Roadmaps is bundled with new 8.20.x LTS, so all good here. Context: update check compares version with MarketPlace, which is old and not compatible with recent Jira. 

To share some updates on this, Jira 8.20 Release Candidate is live and available here - https://www.atlassian.com/software/jira/download-eap 

To share some updates, Jira 8.20 Release Candidate is live and available here - https://www.atlassian.com/software/jira/download-eap The actual release is planned later this month. 

I've updated the link, should be fine. 

Echo @Nic Brough -Adaptavist- point. NEVER touch the files while Jira is running. You MUST stop it first. Regarding the /opt/atlassian/jira/temp/ space, you might want to move to a different mount point with more space, see KB How to Change the Temporary Directory

Hi @Orit Nachshon Sure, please let me help with this part: >In that you mentioned *Not from the normal user* what does it mean? That means, that user sessions should not be part of the redirect config. They should always talk to the same node. >and how do we check this? see the section (How you can check that session…

Hi all, I see that this is some confusion around LoadBalancing, so to prevent the uncertainty please let me clarify some points. :) * To do session affinity at Loadbalancer and redirect traffic based on URL path (/REST), you would need to see request plain text, so as Thomas mentioned you need to terminate SSL on F5 (do…

Hi all, To clarify @Thomas Deiler answer: Everything that carries /rest/api/ in the destination URL is directed to a specific node. Jira UI operations also use same REST API, so you should be careful here and redirect traffic to specific Node4 only from External application (bot), not from normal user. In another case you…

Please note that there was some changes in JIRA 7.x: 'Manage Sprints' permission was added. See related docs: * Using-manage-sprints-permission-for-advanced-cases And KBs: * https://confluence.atlassian.com/display/JIRAKB/Unable+to+manage+sprint+due+to+missing+Project+Administrator+permissions

note 400 ms duration is not tunable: {code} // NOTE: this is only here so we can flag any queries in production that are taking long and try to figure out // why they are doing that. final long timeQueryTook = opTimer.end().getMillisecondsTaken(); if (timeQueryTook > 400) { logSlowQuery(query, searchQueryString,…

Hi Ali, Please see feature request for this: https://jira.atlassian.com/browse/JRA-64974 

We had some problems with https://confluence.atlassian.com. It should be back now. 

Please see updated KB: https://confluence.atlassian.com/jirakb/how-to-merge-jira-server-instances-244352137.html

JIRA bug for this: https://jira.atlassian.com/browse/JRA-43344

In general, JIRA's data model is quite denormalised, so this is hard to come with simple table. This is what could be done for JIRA 6.4 Step 1 // Get list of IssueTypeScreenSchema for Projectsselect sink_node_id, pname from nodeassociation na join project pr on pr.id=na.source_node_id where na.association_type =…

Please be aware of https://jira.atlassian.com/browse/JRA-44588 , Multi Select List and CascadingSelect fields are affected. JIRA needs to cache all values and it's doing in non-optimal way. 

Please see updated KB: https://confluence.atlassian.com/display/JIRAKB/How+to+merge+JIRA+applications+instances

Hi Guys, I've created the suggestion request for this: https://jira.atlassian.com/browse/JRA-45700, please add your self as a watchers and may want to use a workaround. 

This problem looks similar to https://jira.atlassian.com/browse/JRA-62194 Please check if you have same NPE: java.lang.NullPointerException at com.atlassian.jira.plugins.dvcs.util.SystemUtils.getAllProjectKeys(SystemUtils.java:137) It was fixed in recent version of plugin and bundled with JIRA 7.1+

Another method, more complex: (!) Always backup your data before performing any modification to the database. If possible, try your modifications on a test server. * Execute SQL query and find your plugin key SELECT * FROM pluginversion where pluginname like '%text%'; * Execute SQL query and disable plugin: INSERT into…

A couple of notes: * make sure you use JSU 1.4.10+ version, to be able to have required functionality: Copy Value From Other Field Post Function" supports components. * The Copy Value From Other Field post-function should be the first on the list of post-functions for the 'Create Issue' transition,…

Just checked with recent Jira 6.4.4 "-Datlassian.darkfeature.jira.onboarding.feature.disabled=true" works fine Thanks!