Matheus Fernandes Atlassian Team

Karie, Is this what is shown to the user? Does it happen in all browsers or just IE? See: * Layout broken in JIRA 6.0 in all the browsers * Layout Broken in JIRA 6.x in Internet Explorer If this has nothing to do with browsers, can you see if the user has permission to see the issue or if there is any Security Level on…

Hi there, There doesn't seem to be a compatible version indeed. JIRA does have a native functionality though to create links between applications or even external sites, see Creating Links in the Application Navigator. I hope this helps!

It unfortunely is not possible to achieve this by default in JIRA. What you could possibly do is mofify the notification scheme of your project so that your customers do not get a notification email from JIRA when commenting on the issue. I'm not sure how you currently have this scheme set up, but if possible you could…

Hi Ryan, It is actually now possible to configure two custom field contexts with the same project in JIRA - see https://jira.atlassian.com/browse/JRA-6851. Try adding two different custom fields with a similar name (not the same name so you can still search both without causing confusion on the Issue Navigator). I know…

Anytime! :)

Hi Mette, This is actually a bug in the latest version of JIRA Agile in Cloud - see https://jira.atlassian.com/browse/GHS-11412. There are two workaround mentioned in the bug description which you can follow to avoid this error while it is not yet fixed. Cheers, Matheus

The Script Runner Plugin has a built-in post-function to 'Create a Sub-task': This is very similar to "Clone an Issue" above, except that it will create a sub-task. This function could be used multiple times to create several sub-tasks, for instance if you have an issue type that requires approval by 3 groups you might…

Currently the "From" field on the "Contact Administrators" form is only passed as the Reply To parameter in the email, and is not displayed in the email body. You should be able to see the user's email address in the header of the email, or by replying to the email.

Hi Anand, Could you explain further what is that you are trying to achieve with the Jelly Script? Please do use the server path, and also, depending on what you are trying to do, the Jelly Script needs to pass the permission scheme to work, so you may need to add the following to the script: <jira:Login username="admin"…

You are most welcome!

Yes, and you can get a Developer License for any product you currently have by following the steps below: * Log in to my.atlassian.com. * Click the '<tt>+</tt>' sign of your Atlassian product, your account management screen will display. * In the Actions section click "View Developer License." * Review the Developer…

Hi Adam, I have seen a similar behavior that was caused by other incompatible plugins. As you have just upgraded to 6.3.9, please make sure that there are no other plugins installed in this same instance that are not compatible with JIRA 6.3.9. Cheers

Shawn, As in our Licensing & Purchasing FAQ: All installed evaluations include access to our technical support resources. Evaluation keys are for the highest user tier available and are compatible across stand-alone product/add-on user tiers and license types. So this is probably a configuration issue. Make sure that all…

Hi Tomasz, You are indeed correct, as part of fixing JRA-29328 this behavior was added to JIRA, so changes in a JIRA issue fire for both specific events (such as work logged and issue assigned) as well as issue update events. That being said, this has generated more friction that benefits for customers with regards to work…

More info about this on: * https://confluence.atlassian.com/display/JIRA/Workflow+Properties * http://www.j-tricks.com/1/post/2011/02/permissions-based-on-workflow-status.html Check out the second one if you want to make only certain users able to edit during the steps. :)

Mohammed, If I understood correctly, you can get those by using: http://<jira-address>/jira625/rest/api/2/project as per https://docs.atlassian.com/jira/REST/latest/#d2e2043 Is this what you're looking for?

This is a bug in the Support HealthCheck add-on. Please see https://ecosystem.atlassian.net/browse/AHC-48 for the workaround. 

To install GreenHopper manually (without the connection to the Marketplace) you'll need to: * Download GreenHopper - This link is for GreenHopper 6.0.6 (compatible with JIRA 5.0 ~ 5.1.7) * Navigate to Administration » Plugins » Install Plugins; * Click the Upload Plugin link; * Select the GreenHopper .jar you've downloaded…

Monica, There isn't anything in JIRA (by default at least) that could make an user not able to see certain issue types... Check if the same user can see this problem in a different machine and test if a different user can see this problem in this user's machine. Also, as a test, try putting JIRA in safe-mode and see if you…