Laurens Coppens Expert

Olga, As far as i know this isn't possible. I think the only way to achieve this is creating a SD project/customer, but thats probably not what you want. Regards, Laurens

John, You can upgrade directly to 7.9 Only upgrades prior 7.0 require intermediate steps: https://confluence.atlassian.com/ug/jira-software-upgrade-matrix-933696761.html Regards, Laurens

Chelsea, As this is atlassian cloud, i would suggest to open a support ticket with atlassian. Regards, Laurens

Sean, I don't think you can import data from an older jira version. I would suggest to just install the jira 5.0 on the rhel 7.5 server and then upgrade jira on that one. Always worked for me. Regards, Laurens

Ellen, To be able to export a space you either have to be a space admin or a confluence admin. If you have these permissions, you should be able to see the "space tools" menu on the bottom left. Then go to content tools and export. Regards, Laurens

Robert, The licensed users are being mailed by the default jira template settings: https://confluence.atlassian.com/adminjiraserver/customizing-email-content-938847640.html Hope this helps. Regards, Laurens,

Maheeza, You have plugins for this, for example exalate: https://marketplace.atlassian.com/plugins/com.exalate.jiranode/cloud/overview

Greg, You should be able to create a user group and then query with it like this: project in (project name) AND assignee in membersOf("GroupName") Haven't tested it, but should work. Regards, Laurens

Jason, As far as i know this isn't possible out of the box. You can change the layout using plugins like refined theme or ultimate theme. Regards, Laurens

Rick, You are going to change the database of Fisheye, or jira? Since the Tag of this question is Jira Software. When you change your database, you will have to point your application to the new database in your cfg file. Regards, Laurens

If you change the customer request type, it should be visible for the customer, even when the customer request type is hidden in the portal.

Bret, the manual backups and telling the setup wizard to ignore the home dir is indeed the perfect plan (i always do the same) But even then i can still go wrong - hence the restore experience i have :P You're welcome, glad i could help!

On the confluence space you have to give your confluence user "create page" permissions and then it should work. Also found this other link: https://community.atlassian.com/t5/Answers-Developer-Questions/How-do-I-make-the-quot-Create-KB-Article-quot-button-show-in/qaq-p/491802

Ok, so part 1 is covered. Then you need to make sure that your service desk agent has read-write access on the confluence space that is linked

Yeah, been there before, the chances of getting it working without the rollback are very low. Experience teaches me you need to get it working again in the original condition before retrying the upgrade. And making sure you have enough diskspace ;-)

Bret, I would suggest to restore to the working 7.2 and then retry the upgrade. So reinstall the tarball and restore the database.

Hi Joanna, It depends on the notification scheme, but normally you have a "role" called project watcher, then they should get a notification.

Damir, Is the jira SD project linked with a specific confluence space? You have to do both: The applink and the linking on project level.

Yves, When you move an issue from incident to another issue type, the customer request type will be empty. You will have to set it manually or create an automation rule for that.

Philippe, Thanks for sharing! Glad to hear it is resolved.

Laxmi, I think the easiest way to do this is just hide all the customer request types. Then they will still be able to see the old issues, but can't create new ones. Regards, Laurens

Hi, What database are you using? The log says its probably database related. Regards, Laurens

Robert, I struggled with this as well, sad news is, this isn't possible in standard jira service desk (how crazy it sounds). You can however use the intenso extension plugin to hide the field on the creation of the issue through the portal, and make is visible again once an agent has updated the field.…

Hi Adi, You can use the admin helper -> where's my field to see why the field is visible (on which screen). Then you can just click on that and remove it from the screen. https://confluence.atlassian.com/adminjiraserver071/jira-admin-helper-802593078.html Regards, Laurens

if it is a cloud instance you have, i would try to open a support call. If it is server, i would find it very odd that it is blocked

hmm, weird, i use the paid version on server, what version are you using?

You have a "Version Created" trigger in the automation plugin, its on the creation of a new rule bottom right.

Yes, service desk customers.

You only have to license the "Active" users in crowd, if you disable the user in crowd, it will still be linked to the old jira issues, but not longer active in jira and other apps, so no longer licensed. You pay for all the users that have the ability to authenticate to one or more apps connected to crowd. So you have to…

Hi, 1. As all of your users and groups are already in ldap and in crowd, you should be able to connect jira to crowd and then just put the priority of the crowd directory higher then the ldap directory, same for bitbucket. 2. You only pay for the active crowd users. For example if you have 300 unique jira users and 200…