David Yu Expert

That won't be enough as the requests will not be coming from localhost. They'll be coming from the end-user. Somewhat related but you may also be interested in this: https://community.atlassian.com/t5/Jira-questions/What-s-the-best-way-to-require-login-on-every-page/qaq-p/765834#M248511

I believe sometimes the browser itself will make calls to /rest/api/2. For example, just loading the Rapid Boards I can see a request to /rest/api/2/project. Maybe you could inspect the referrer as most browser generated ones will have a value? I guess this is good preventative measure to prevent users from integrating a…

Hi Greg, did you also consider C5 instances as well? It seems like it has a good ratio of vCPU to memory that might benefit in our usage scenario where we get large occasional bursts of activity.

Re-opening an old issue here, but are you sure that Stanza actually works? Testing 3.0.6, it seems you can use any user regardless of what's in the Stanza.

Good find! I'll have to give it a try. I'll need to double-check all the path patterns it protects. Still looking for similar option with Confluence.

My guess would be the BotKiller plugin. You can always test disabling it to see what happens.

I mean I wish to guard pages which are open to anonymous users. For example, look at all the Jiras in the wild. I know it's not exposing internal information, but it's still data I don't want exposed to anonymous users. https://www.google.com/search?q="AboutPage.jspa"

It's interesting how your user smithj is getting a new sessionid on each request. Does he have cookies enabled or some weird browser extension installed?

Vote on this: https://jira.atlassian.com/browse/JSDSERVER-931 It's a limitation in the licensing scheme. Only full fledged agents can do anything useful with tickets which is a bit bizarre.

Go to Administration > Manage Plugins > System Plugins, and look for: Atlassian JIRA - Plugins - Gadgets Plugin Expand the module list, and try to disable the "Assigned to Me" module.

I think I found a way. The images are saved by md5 of the fisheye username. They are then saved under the first two characters of the hash: var/data/avatars/XX/md5hash.image Can anyone confirm or deny this is OK to do as long as the image is under 2MB?

You would probably get some improvements in repository scanning since you can bypass HTTP and use the file protocol. If your repository is small, you probably won't even notice the speed benefit.

To ungrey the SSO checkbox, you need to have this in your nginx config (assuming SSL terminated at nginx) proxy_set_header X-Forwarded-Proto $scheme;

Think I found the answer...it's a bug. A tangled one at that: https://jira.atlassian.com/browse/CONF-29968 https://jira.atlassian.com/browse/CONF-28726 https://jira.atlassian.com/browse/CONF-30007

But I can't expect end-users to know this...I can't predict what macros users will put inside my user-macro. Maybe the question I should really be asking is: are other macros supported inside a user macro?

Yes, we're waiting for the features from this fix: https://jira.atlassian.com/browse/CWD-4337. Last release of Confluence 5.7.4 contains 2.8.2. The latest JIRA is also stuck on 2.8.2.

I use a SQL query to scan JIRA's change history. If issues have their versions changed to the sprint I've locked, then I'll see it in my report.

It could be a permission issue. Check your JIRA permissions schemes and see if you have either the Close Issue or Schedule Issues permission. GreenHopper can be configured to use one of these two permissions. http://confluence.atlassian.com/display/JIRA/Managing+Project+Permissions

Going by my memory, the user licenses between JIRA/Crowd does not need to match. Is it possible you have usernames that clash or exist in both the Internal and Crowd? If so, you'll need to ensure the order of the directories are configured correctly in JIRA so that it auths against Crowd first before trying the Internal.

Indeed it does. I made a visual mistake by onnly scanning at the FROM: header, and not the REPLY-TO:.

I'll go ahead and plug Brenden's plugin here: https://plugins.atlassian.com/plugin/details/19471

I suspect you can with this plugin: https://plugins.atlassian.com/plugin/details/68723 You'd associate a JIRA transition to a Crucible Create Review event.

Actually, they might be right; I'd incorrectly assumed the users would stop showing up in the reporter list if they were deactivated. Sorry! I guess you'd have to bulk-reassign the legacy user's issues, and then DELETE the user. :-(

If you just want to make these users not appear in the reporter drop down, you can just disable the user. In the latest JIRA, you can deactivate a user. In order ones, try removing them from all groups. As for issues they currently have assigned/reported, you'll have to bulk-reassign them.

It actually doesn't matter which user you install FeCru with since you are given the opportunity to upload a private key file when you add your repository. So you can just generate a new ssh key-pair with ssh-keygen. Put the public one in gitolite, and use the private one for FishEye repos. I create all my repositories in…

I use gitolite with FishEye, and it works fine. You simply create a service user, generate a private/public key. When creating a new repository, you will specify the location as "git@gitserver:location/repo.git" You can then upload that private key to FishEye during creation of this repo. One thing to watch out for is the…

I've been enjoying OpenNMS. It's lightweight, hooks right into JMX (no client to install), lives outside of your atlassian app so it can measure anything exposed in JMX (you can poke around with jconsole). To monitor additional performance indicators, you can install a SNMP client on each host...I've got it monitoring disk…

Yes, look at the Script Runner plugin + Post Functions. Not sure how maintainable this will be for you long term. Also not sure if this is a great idea long term as every issue you create will have non-null values. Also have a look at some of the workarounds here: https://jira.atlassian.com/browse/JRA-4812 Certain field…

According to the docs, all links should update automatically when you move or rename a page. You just have to make sure your links are not web-links that start with http...use Confluence page links instead. https://confluence.atlassian.com/display/DOC/Moving+a+Page…

I don't quite follow, I always thought you could upgrade a XML backup, even if it's an older version: https://confluence.atlassian.com/display/JIRA/Restoring+Data Only project imports require that the source XML backup is from the same version. You shouldn't need a 3.12.2 license.