I have the latest JIRA software version 7.1 self-hosted. No matter what I do , I can t see the upload add-on button. We also have a previous 6.xx something version and on that , to see the upload button I had to disable marketplace.Atlassian.com access. I tried that on this version as well , but it did not work as intended. Can I have some help ?
EDIT1. When I go into Add-on setting , If i try to disable/enable Atlassian Marketplace I get this error:
Your request cannot be completed at this time.
Logs are not saying anything about this error. Any ideas?
Ok, that's good (I had feared you were using a Cloud download, which would kill the upload option)
But it does leave me a bit stuck - I don't know how to disable the upload function cleanly without causing errors that you'd see in the logs, except by logging in as a non-system admin. Disabling the whole UPM will do it, but you've said that makes the option appear in 6.4 which is the opposite of what I get.
Could you check that all the modules in the UPM are fully enabled though?
To check the modules, go to manage add-ons, find the upm and look to the right, it will say X modules of Y enabled (for most add-ons, X = Y, but not always). Have a look at any disabled ones.
I really don't know how to get rid of "upload add-on" though, except by being on Cloud.
Oh, one other thing that I didn't know until I ran into it a minute ago.
Could you have a look at your system information page and find the JVM input argument settings? It might be called something different on your system, depending on version, so here's the first couple of lines from the JIRA I'm looking at today - lots of the options will have -D or -X on the front of them:
JVM Input Arguments -Djava.util.logging.config.file=/opt/jirahome/install/conf/logging.properties -Xms1024m -Xmx2048m -XX:MaxPermSize=512m
|JVM Input Arguments||-Djava.util.logging.config.file=/opt/atlassian/jira/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Xms2048m -Xmx2048m -Djava.awt.headless=true -Datlassian.standalone=JIRA -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true -Dmail.mime.decodeparameters=true -Dorg.dom4j.factory=com.atlassian.core.xml.InterningDocumentFactory -XX:+PrintGCDateStamps -XX:-OmitStackTraceInFastThrow -Djava.endorsed.dirs=/opt/atlassian/jira/endorsed -Dcatalina.base=/opt/atlassian/jira -Dcatalina.home=/opt/atlassian/jira -Djava.io.tmpdir=/opt/atlassian/jira/temp|
Ok, it's not what I ran into; there's a -D flag you can set that removes the "upload addon" function.
I'm afraid I have to go back to "your UPM is broken". You've ruled out all the possible ways to disable the upload addon function, and there's nothing in the log, so I don't know what's wrong. All I can think of to do next is increase logging in the UPM to "debug" level so you can see what it's doing - that might tell us a bit more. Admin -> logging and profiling -> Configure logging level for another package and add com.atlassian.upm with "debug" level
I finally found the issue that was bugging the jira/confluence server.. Having an nginx proxying all requests, we let only methods POST/GET , but as we found out JIRA is using much more methods(eg. PUT), so we excluded that from the server. Thank you for your time and for your understanding
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs