Comments
-
Yes . SQL 2016 is supported by JIRA . So it doesn't matter if you run 7.2.4 or 8.5 on it - it anyway supports both. It is same as doing the JIRA upgrade first and then upgrading DB - so no issues.
-
While you try to load next time or refresh the gadgets - check the logfile and look for error message during that time when it loads for a new data
-
1) Increase the cpu core to 4 and observe the change in behaviour. 2) Do you see any performance issue when there is a cpu spike ?
-
I am making a wild guess - maybe the issue is shared in multiple projects/boards with varying permissions ? Not sure though
-
Careful though - if you are running it on business hours or have large users accessing JIRA right now - I'd advise your run them later, specially the workflow portion.
-
Try running an integrity check or have you already ?
-
Maybe the user id you used to install JIRA previously was an administrative user with higher privileges . And the machine user id you are using now does not have administrative permissions to work on those JIRA folders. Use a user id that has full admin permissions in the machine or atleast in those folders. Or ask your…
-
Have a look into this plugin . https://marketplace.atlassian.com/apps/1215443/sync-service-manager-with-atlassian-apps?hosting=cloud&tab=overview Looks like HP Oneview waa renamed as HPE Oneview and then Integrate Micro Focus Service Manager (formerly HPE).
-
Why don't you make it 4 and see if it improves
-
By the way , your server has too many applications lol
-
So it doesn't look like Confluence is the problem there. CPU usage seems to spike at every instance of any process running in that server. How many CPU cores does the server have ? Maybe you can work on it and hike it .
-
Can you run a grep on confluence user and also on java processes to show us what all java processes are running and what all processes are owned by the user id confluence.
-
/data/attachments ... try copying this too..and ../avatars/ too
-
You will have to copy attachments separately - it is not a part of your normal backup
-
Please validate your board filter - that is what helps the board pick tickets. If you think the board filter is correct - contact atlassian support as you are on atlassian cloud.
-
1) Always recommended to upgrade to the latest version as it would consists all the latest bug fixes. 8.5 is the latest JIRA Software Enterprise Version . I'd suggest you maintain (n-1) version - that's my personal strategy to keep one version older than the latest. Note : Read the release notes to ensure what changes are…
-
Have you tried importing the ssl certificates in to jira keystore ? Try that - reboot JIRA and check your gadgets once again.
-
Login to this using your credentials and check if you can recreate a new evaluation subscription https://my.atlassian.com/product
-
Have you purchased subscription before or were you on evaluation ?
-
I think I will look at this way. I will create project c with board c - board c shall be configured ( in filters) to pick issues from project a and project b . The sprint running in project C will include issues from both A and B. That would be my way of doing it. Others may have a better idea maybe. But do ensure that "…
-
I agree with Ismael. If you have a testing environment - go through all upgrade manuals and do a test upgrade manually that would give you some confidence and go ahead with your upgrade manually; Note 1) Take care of backups 2) Take care of plugins 3) Take care of any customization that you have in place .
-
Hello Kensuke, There are certains things we will have to check first ; 1) Did you do the installation and configuration of this JIRA environment ? 2) Is this JIRA environment connected to any external user management system ? If you are the admin, you can check and verify . If not, you will have to do the connectivity. 3)…
-
I am surprised - how did you get the same ID :p . Did you just import the backup on an already cloned JIRA ? or Did you do the JIRA installation from scratch ?
-
Dear Kensuke, When you shared initially that there are already members who see the following message ; This user account is managed in an external User Directory and Jira is not able to update your password. Please contact your System Administrator if you have any further queries. I think your JIRA environment is already…
-
For a moment, I thought even ex British PM uses JIRA :p - I had to check your profile haha
-
Thanks - something for us too to learn .
-
I'd suggest you to give this plugin from Atlassian a try - it's called Portfolio for JIRA. https://marketplace.atlassian.com/apps/1212136/portfolio-for-jira?hosting=cloud&tab=overview
-
Why don't you do a separate install and just import using the backup or use a database backup ? I bet that is the best way to go about - you already have second valid license.
-
My understanding of how atlassian works is - you should ethically have one license per server id . It isn't quite right to have two production instance running same server id and license. why dont you move over to data center - buy one license and create as many cluster nodes as you like to and run them as production.
-
1) Yes - you will have to separately upgrade software and service desk. 2) Looking at your current software and service desk versions - you can directly upgrade to the latest versions - you need not follow any order. 3) After you upgrade Software - it is pretty easy to upgrade Service Desk, it is just a click effort.