Vickey Palzor Lepcha Expert

Is is working when you bypass PROXY using your IP and port ?

Wouldn't that diminish your user experience ? JIRA is the World Cup while Trello is like a County Soccer :-)

Making an attempt to answer questions - recreating scenarios from questions asked and troubleshooting them to find a solution. That is my method of knowledge sharing :-)

Try increasing your memory allocation - addition of Synchrony causes huge memory usage in Confluence Check your proccesses - see if everything has been clean shut down. Kill all your confluence process and try starting once again.

@Danyal Iqbal I don't think running them on the same machine is a bad idea. I have been running them for ages now with no problem at all. There could be only one issue - performance, but that's not an application issue, which can also be taken care of by pumping up the server resources.

@Dave Norton Great job guys.

I'd have stayed with Apache HTTP :p - at least I am fond of it and find it pretty easy.

I would say - restore from backup in a test instance - sort out the deleted issuetypes and reimport it back to your production instance - that would retain your current data atleast and not override them

@Matthew Davis Hey 7.10 is out :-)

Well Thu - I suggest you do the following; * Release this upgrade note for 6.8 https://confluence.atlassian.com/doc/confluence-6-8-upgrade-notes-946014208.html * Read the release note for 6.8 https://confluence.atlassian.com/doc/confluence-6-8-release-notes-946014166.html * Do an upgrade in your Test Instance if you are…

What exactly are you interested in knowing ? You mean the process - problems - feature ?

* For xml - user your JIRA admin console to export and import * For attachments - simple linux commands for copying from one server to another ( hope you are aware of where attachments are in a JIRA environment)

Just a check my friend - just check the system info and see if it's the right base url - test base url and not prod base url. LDAP is a type of Active Directory solution - just validate that it is pointing to the correct AD and not the Prod AD. These are just check you need to be sure that no PROD configurations are…

* Just take an export backup from Prod and Import the same to Test. * Attachments - copy the folder manually. * After import, log in and reconfigure settings and sorts. Validate - base url, ldap settings, licenses and so on, check applinks if any .

I hope you did not miss the jdbc driver - that is a very well known issue during DB connectivity.

I'd say go through the release note :) https://confluence.atlassian.com/jirasoftware/jira-software-7-9-x-release-notes-946034808.html New version will obviously be better with fixes and improvements - you would be aware of whats new and what has been fixed by reading the release note. * Upgrade your test instance first -…

10 ? The latest we have I guess is 7.9.2 . I am talking about JIRA Software Server

And your apache configurations should have something like this ; ProxyPass / ajp://localhost:8009/ ProxyPassReverse / ajp://localhost:8009

I don't think what you've shown above is for AJP

Did you uncomment the ajp connection line ? your protocol doesnt say AJP . It should be something like this ; <Connector port="8009" redirectPort="8443" enableLookups="false" protocol="AJP/1.3" URIEncoding="UTF-8" 

Did you enable it on your server.xml ?

How about your ajp ? Did you enable them ?

Rather expensive :p - and training materials once purchased should have been available for at least a year if not forever.

Have you checked/updated your jdbc driver ?

I refer you to please read the release notes for the versions. There will always be an enhancement in a newer version - it's obvious. 7.9.2 will obviously be better than 7.1.10 

Can somebody help me understand this please ?

Also I believe a user should have Move Issue permission in source project as well as destination project for " Move Issue between Projects" to work - I guess, that's what my common sense says :p

@Moses Thomas I understand that " Move Issue " permission allows us to move issues between projects. But I am confused about the second part of the definition - between workflows of the same project. 

What I normally do is use my Board Filters to pull in data to Confluence - then switch to JIRA Chart view - that way my JIRA Data is pulled in and displayed as Pie Chart, Created Vs Resolved or Two Dimensional. Just an elementary usage though.

JIRA and Confluence both run under the same basic principle and concept - you can do the same with Confluence too.