Brant Schroeder Community Champion

You can go here and make a product feature suggestion: https://jira.atlassian.com/secure/Dashboard.jspa?selectPageId=10440 I searched the current suggestions and this is what I…

Sounds like something is corrupt. This should help you out https://confluence.atlassian.com/confkb/confluence-triggers-npe-when-a-user-tries-to-open-view-all-users-802597745.html

You will need to use a plugin such as ScriptRunner to accomplish this. Since the approval is already in a workflow transition you can add it as a post function. The post function can evaluate the field and then auto generate the issue using ScriptRunner.

Ensure that you are using Java 8. Also confirm the Java class path has been setup correctly.

You would need to use something like scriptrunner and create a custom script to make the change.

You will need to stand up a new server and install the same version of the Jira application on the new server. You will then need to stand up the DB. Once the DB is up you will need to migrate the home directory files and any customizations into the new instance. Connect the new instance to the DB and start the…

Sounds like the rest api is not working correctly. This is often caused by an incompatible app (plugin). Make sure that your apps are upgraded and any incompatible apps are disabled or uninstalled.

My understanding is that they have to be a confluence user or you are not really adding them to the list of individuals that the page will be shared with. https://confluence.atlassian.com/confcloud/share-a-page-or-blog-post-724765345.html

You can add code in Confluence as an admin to the footer by going to Confluence Administration -> General Configuration -> Sidebar, header and footer You can add the code their. It would be the same code snippet for all pages.

The error shown from the server logs usually means that the authentication credentials supplied for the SMTP server are not correct or have expired. Did you happen to use different credentials at first? Here is a help article…

It is available in the latest version of Confluence. https://confluence.atlassian.com/doc/office-excel-macro-375849173.html Please ensure that your Office Connect Plugin is enabled.

You will want to install the same version. I am assuming that you will have access to the files or a backup of the old instance. After you recover you can update. Here are some additional resources that can help you…

This page will help you out: https://confluence.atlassian.com/adminjiraserver073/advanced-use-of-the-jira-issue-collector-861253497.html?_ga=2.61672872.528327540.1556810616-1785046573.1549295491#AdvancedUseoftheJIRAIssueCollector-FullSourceCode Scroll down to the section titled embedding multiple issue collectors.

You should be able to use the production key on both instances for a short period. I usually update the legacy system to developer key then place the production key in the new production system to prevent any issues. This will require you to update plugins with development keys as well.

You will need to use your production key in the cloud production issue. Once you complete the cut over you can update your old on prem instance to a developers license until you shut it down.

Please check the following: * Does the issue have a request type? If you do not have a request type no customer emails will go out. * Check and make sure that the customer notifications are configured properly in the service…

Have you reindexed since you updated?

The user needs to be in the browse users and groups permission group. Note the "Browse users and groups" permission is a global permission, not managed through permission schemes as are most of the permissions. Usually you assign a group to this permission so make sure that use is in that group.

You will want to ensure that your notification scheme is configured correctly. By default if you are assigned an issue then you should be notified if your outgoing email is setup. Learn more about notification schemes here: https://confluence.atlassian.com/adminjiracloud/creating-a-notification-scheme-776636401.html Learn…

You can not remove portals technically but you can hide them using permissions. In the project settings you can change the Customer permissions. Who can raise requests? --> Customers who are added to the project Then remove all customers from the permissions. I am assuming that you are not using the desk anymore.

Did you try this yet? https://confluence.atlassian.com/confkb/broken-avatars-icons-in-confluence-after-an-upgrade-329974322.html

Do you have any plugins or automations that are running under the user that made the change?

If you have a license for Jira Software it needs to be installed on top of Jira Core. If Jira Software is failing on install like it is for you then you need to look at the logs on the server and see why it will not install. Jira logs are stored in the home directory in the log folder. Viewing the logs at the time of the…

It could be one of two issues: * You changed your Jira user directory settings. For the AD (LDAP) directory there is a setting to add user groups automatically. You can set this up so it automatically applies the group you are using to provide a Jira license, jira-core-users for example. You can learn more…

If you are not planning on decommissioning the old box you will want to update it's license key to a development key. Then you can apply the production key to the new server. Get the development key - https://confluence.atlassian.com/confkb/how-to-get-a-confluence-developer-license-152044449.html Change Confluence License…

After setting up 2-factor did you follow these steps for the less secure app https://devanswers.co/allow-less-secure-apps-access-gmail-account/

If 2 factor is turned off it will not need an app password, just the account username and standard password.

You said that two steps was turned off?

Are you using Service Desk cloud?

Are you cloud or server based? Also is this the first time you have setup an email account on this instance?