Tweeting your Hints and Tips – Tips via Twitter

Do you have hints and tips about your JIRA bug tracker to share with the world? Even more, would you like to see your tips appear on a page in the Atlassian documentation? Just tweet with the hash tag "#JIRATips" and see your hint appear in our documentation. Then grab a badge for your blog!More...

search.twitter.com

Blogging your Technical Tips and Guides – Tips of the Trade

Have you written a blog post describing a specific configuration of JIRA or a neat trick that you have discovered? Let us know, and we will link to your blog from our documentation. More....

Contributing Documentation in Other Languages

Have you written a guide to JIRA in a language other than English, or translated one of our guides? Let us know, and we will link to your guide from our documentation. More....

Updating the Documentation Itself

Have you found a mistake in the documentation, or do you have a small addition that would be so easy to add yourself rather than asking us to do it? You can update the documentation page directly.

Getting Permission to Update the Documentation

Our Style Guide

How we Manage Community Updates

Here is a quick guide to how we manage community contributions to our documentation and the copyright that applies to the documentation:

Monitoring by technical writers. The Atlassian technical writers monitor the updates to the documentation spaces, using RSS feeds and watching the spaces. If someone makes an update that needs some attention from us, we will make the necessary changes.

Wiki permissions. We use wiki permissions to determine who can edit the documentation spaces. We ask people to sign the Atlassian Contributor License Agreement (ACLA) and submit it to us. That allows us to verify that the applicant is a real person. Then we give them permission to update the documentation.

Copyright. The Atlassian documentation is published under a Creative Commons CC BY license. Specifically, we use a Creative Commons Attribution 2.5 Australia License. This means that anyone can copy, distribute and adapt our documentation provided they acknowledge the source of the documentation. The CC BY license is shown in the footer of every page, so that anyone who contributes to our documentation knows that their contribution falls under the same copyright.

6 Comments

I was one of the earlier Atlassian partners who signed up for the ability to edit the documentation. It's really been very satisfying to fix errors and add helpful new content right there and then. When a client complains about something on a page being wrong, I log in and fix it. That raises a few eyebrows sometimes (in a good way). I'm also happy to have the whole Atlassian Tech Pubs team at my back, in case anything too odd or US-specific creeps into my edits.

This is typical of Atlassian's open company approach to things - monitor carefully but expect to trust your partners and customers. Kudos to them.

Anonymous

Log Scanner

Cause

The possible culprit of the problem is because there is a whitespace included at the end of the project key pattern, or the pattern is not correct. This is defined in the jira-application.properties file.

Resolution

Open the jira-application.properties file.

Find the jira.projectkey.pattern parameter, confirming that it is the correct regex and also remove the whitespace if there is any.

Please correct according:

Running JIRA 5.1 I found out, that the only place the jira.projectkey.pattern is used is in file webapp/WEB-INF/classes/jpm.xml.