Comments
-
You can not upgrade server to a version that is released after the end of your licence. Imagine your licence ends today, and you do not renew the maintenance. Let's say you are on Jira 7.8. You can upgrade to Jira 7.12 because it was released before the end of your licence. You will NOT be able to upgrade to the next…
-
Yes, that's all you need.
-
If you are happy to run unsupported by Atlassian, then yes, you can not renew However, you say >We usually just upgrade our server by ourselves That will stop. You can't upgrade to a version released after the end of your licence.
-
Install Jira. Do not install any add-ons. Go to the list of add-ons and see what has been installed "off the shelf".
-
This is the same question as https://community.atlassian.com/t5/Jira-questions/jira/qaq-p/906791 Except that you can track Apps that only provide macros - you can search for macro usage in Confluence.
-
You need to look at each one individually, and you need to understand that many are not used in projects. An App could be providing all manner of functions, and how you might want to count "project uses this" has different routes and complexities. As a non-exhaustive list, consider these: * App that provides workflow…
-
Not what I asked. Do you get the right list of issues when you try the query in a search?
-
Check the automation rules, they let you do some changes to issue type.
-
Admin -> application links
-
Some of the "off the shelf" plugins are added as user-installed. You'll need to read the descriptions of them to see what they do.
-
OK, two things we need to check before we can go further. 1. Are you using the time tracking fields, or are your estimates done on something else? Could you run a simple test - run a search that returns (at least) one user story and its sub-tasks. In the issue navigator, add the columns "Remaining Estimate" and "Σ…
-
I've got the same questions as @Aaron Williams - I joined all the groups I wanted to join when they arrived (pretty much "all but the location groups where I am not" and "cars")
-
This is usually down to users. The most common culprit is when someone logs in as root, and (re)starts Jira under that account rather than the jira account. This clobbers a load of the installation and working files, including the pid file. With root taking ownership of them, when you try to stop/start Jira as another…
-
Also, as well as permissions, you have quite a complex query which might not be doing what you expect it to. Does it show the right list of issues when you use it in the issue navigator?
-
No, you'd need to hack the code to increase it, and you can't do that on Cloud
-
You don't. There's no mechanism for arbitrarily downgrading Jira for random users. If you don't want them to see things, you have to hide the issues, using permissions and security scheme.
-
Ok, so you can add it.
-
That is done in the permission scheme, and you can select users, groups, roles, etc the same way you'd set any other permission. I'd strongly recommend using a role. Also, note that users can only set security levels they belong to.
-
The remaining estimate in your report is the "remaining estimate" for the current issue. You should adjust your report to use the "Σ remaining estimate" field.
-
Those are warnings, not an error telling you why confluence is not serving. Have a look at both the application and server logs in more detail - <confluence home>/logs/atlassian-confluence.log and <confluence install>/log/catalina.out
-
No, the data is not stored. The audit log is the only place these things are recorded.
-
I don't know, it depends on how you have done it.
-
I'm afraid not, it's gone now. You might not have set up any backups yourself (you really really should do that!), but off-the-shelf, confluence takes regular xml backups. Check <confluence home>/export for them.
-
Use the issue navigator. Go to issues -> search and run a search (such as "project = x"). You can select what columns to display by default, and if you save the filter so you can run it again without having to build the query again, you can save the column layout with it.
-
To do this, add an issue security scheme as per docs - see https://confluence.atlassian.com/adminjiracloud/configuring-issue-level-security-776636711.html However, I would not create an "all project users" level, as it is totally unncessary - to use it, your users just need to not set a security level.
-
You can't - the access is not done by route, it's by user. If a person can use the system, they can use the gui and REST api.
-
You need an admin to add the field to the "create" screen for the incident issue type.
-
Jira cannot work at all without a "jira home", so if the old version is running ok, there is one somewhere. Try the "system information" page in admin, that will tell you where it is installed and what you chose for jira home.
-
There are two separate questions here, but: > How can I create a status category? You would need to hack the core of Jira to add a new status category >but not able to assign status Status is an indicator of where an issue is in its workflow. To "assign a status", you move the issue through the workflow to the status.…
-
The change of disk space is not the cause of this problem. If you had decreased the space to a point where temporary files could not be created or used, it might be, but as you've increased space, it's not that. Yes, you can migrate your service to another machine, see…