Brant Schroeder Community Champion

You could add a custom field (Checkbox) to the screen being used by that project to create issues that contains the URL to the confluence page in the option of the checkbox field. I don't think it would be clickable though.

Marc, I believe that you will have to contact them to have them convert the plan. You can contact them on their pricing and billing support page.

have you checked the logs to make sure that everything started properly?

Are you running on Linux or Windows?

Atlassian fixed the issue and after upgrading the issue went away. What version are you on?

Jay, I know you are trying to get to an @mention operation for security. I don't know of a way other than watchers to make is so individuals can be added and see it once they are added to an issue but not have global read only access. You are correct that this will only work server and not in the cloud. The [~username]…

I do not know of a way to exclude certain search operators. Atlassian support might be able to let you know if this is something that can be changed in a config or not.

William, ? is used as part of Confluence search syntax. It is used to replace a single character. From their documentation - To replace a single character in your search, use a question mark (?) as a wildcard, For example, to search for 'butter', 'bitter', 'better', or 'batter'. Use b?tter. You can learn more…

By default Jira does not provide a way to do this. You can however use this free plugin - Jira Watcher Field. It adds a new field type that you can use in permission schemes, Issue Security Schemes etc. It will make it possible to grant various access to watchers on specific tickets. You will need to do the following: *…

Ganishka, You can use an automation in Jira service desk to accomplish this. You would do it on issue creation and if they are in a specific organization you could then change the assignee. The issue is that organizations need to be managed manually in Jira at this time and a group that is pulled in from AD cannot be added…

Glad to hear you got it working.

Aerik, I am assuming that you installed the following add-on https://marketplace.atlassian.com/plugins/atlassian-jira-training/cloud/overview Once the add-on is installed you should see a training link on the main Jira navigation next to the create button. You can access the training by clicking on that link. 

Kavitha, Do you have access to the server that the Jira instance is installed on? If you do please try opening the marketplace URL in a browser. https://marketplace.atlassian.com It sounds like the server is being blocked via firewall rules.

Since you are uploading the CSV to the cloud and the application is processing the CSV the file location has to be something it can access publicly.

Irma, Atlassian Cloud uses Atlassian IDs. These are accounts that are managed by the user. He or she should be able to change his or her email address by going to http://id.atlassian.com

If you are running Jira Core as a server installation this is often caused by a firewall rule. Ensure that the server has access to external sites specifically the marketplace.

There are 3 plugins that you need to disable to be able to remove HipChat integration entirely. * base-hipchat-integration-api * base-hipchat-integration-plugin * hipchat-for-jira. If you disable those 3 plugins it will no longer show up on Jira issues. IMPORTANT: You need to be sure that you have never set a workflow with…

The files have to be publicly available. You need to either have them accessible via http and specify the URL. The location you are providing is local to your computer and Jira Cloud cannot access them. If you can place them on a public web server you can update the file locations and the CSV import will work. Helpful…

I don't know of any way to do it dynamically without using a third party plugin. 

Felix, I would use scriptrunner to make this change on post create function. I would also ensure that the two custom fields are required. I think it would be something like this issue.setSummary(field1Value + " " + field2Value) You can learn more here about the…

Did you try changing the JIRA "Default user time zone" under "General Configuration" to see if this resolved the issue? If you are using cloud I believe this is what you have to do to resolve the issue.

Elif, This has to do with JIRA using the default user time zone. You can find information about this here https://jira.atlassian.com/browse/JRASERVER-59495?src=confmacro The path to change the timezone is Admin, System, Settings, Default user time zone

Mark, Just checked it in multiple browsers and it is working fine. Have you tried clearing your browsers cache? Maybe Atlassian made a change to their site and the cache is giving you problems.

Quan, I would do a fresh install of the same version of JIRA. This will create the database for you. You can then point you JIRA instance at the new DB. If you do this there will be lots of issues. if you do not migrate the DB content as well. I think it would be better to address the issues you are having. Can you explain…

Zsuzsanna, A request type is associated with an issue type. I would create an issue type for the request that you are putting together in the service desk portal. You can then create a screen scheme / issue type screen scheme and associate the proper screen with only the issue type you would like those fields to show up…

Bruno, Since dashboard gadgets are fed from filters and there is no way to pass a variable to a filter, there would be no way to do what you are describing even with a page reload. We have project reports in Confluence that feed from Jira that I think accomplish what you are trying to do. When we have a new project we add…

I had this issue before and I changed the password on the email account and reentered all of the information and everything began working again. Try this and see what happens.

This is the community forums where users and Atlassians can respond to issues. Actual support tickets can be submitted here: https://support.atlassian.com/contact/#/

We setup our aliases so that they come in with the regular email address and are added to the issue as a request participant. We then use an automation that triggers on create. When a request participant of the specific email alias is found we then either apply a request type or on service desks with lots of email…

When you installed Confluence did you just use the embedded database? If so you can access it using the following documentation and then query the tables listed above. https://confluence.atlassian.com/doc/embedded-h2-database-145098285.html