Comments
-
Status is not a simple field (and rightly so). It's an indicator of where the issue is in your process. You can only change status by using a transition to move it through the workflow. Personally, I'd like it to be easier to transition in some places, but I do get that it's not trivial
-
Ok, looks good, can you show us all the permissions for the space (fuzz over any user names that might be in there, and parts of group names, if you have any security worries. We only need the full list and an idea of the rules about who can do what, not which <identifiable person> can do what)
-
Go to the permission scheme and make sure it includes the two groups in the "can create issue" permission. I strongly recommend that you name a role in that permission in the scheme, and then go to each project and add both groups into the role. (Bit more complex to set up, but minimises the number of schemes, and lets…
-
That means roughly what it says. The account you are using for this integration has tried to login and failed too many times, so it is looking like a security risk. Either try to log in as that user and pass the tests, or login as an admin and go to user management and set their attempts back to zero. You will need to…
-
No, I get it, you're trying to ignore "minor" edits. Confluence does not do that, it records a full and (hopefully) accurate log of all revisions. You might not need that, but to a lot of people, it really matters. To most of those who don't need it to be so strict, it also does not matter that there are loads of versions.…
-
I am sorry, but you are missing the point. Please re-read the numbers in the url and the error message you gave earlier. They are different, so it looks like you are giving us an edited response from an incorrect url, or an edited url with a different response. Try the right url and give us the actual error.
-
No, because the module would be being misled by the same problem.
-
Please, read the first paragraph of my answer.
-
"one of the licence"? Server only has one licence, as you can only run one system per licence. Could you explain *exactly* what servers you have and how they are datacentre or not and how they are linked together?
-
I asked this at the last summit. Third-hand, it's unlikely to happen before the next US summit at the earliest, and there was some doubt that it would happen at all. So, no, there's nothing resembling an ETA for it
-
I'm afraid I could copy and paste my previous answer. You need to define "unable to edit" and you need to check the permissions and restrictions (admin rights give the user admin rights, not other rights)
-
See https://confluence.atlassian.com/support/atlassian-support-end-of-life-policy-201851003.html Please be aware Atlassian doesn't do "stable" versions. They do it the right way - they simply release, not bugger around with pointlessly noisy arbitrary releases. (And, yes, they do early access stuff, but you have to…
-
It's usually the class key or the menu-item definition, but it can be all sorts of things. There's no way to "force" anything. It can't be done. Imagine you have a library where you can't find a book because it's got the wrong classification. It's not in the library because it thinks it's a badger and libraries don't…
-
There is no project export. You'll need to get a full backup from the admin -> backup/restore section. Project import can import single projects from that.
-
It is not. To work with issues in Software and Business, or the issues behind the requests in Service Desk projects, you need to be a Jira user, not a customer. Although, if you reconfigure the mail handler to default a "reporter", then you can allow them to raise issues effectively anonymously
-
Use a well supported and well-known one. We tend to find most people run Production on RedHat because you can get support for it, and then CentOS for dev/test. Nothing wrong with using CentOS for production though, and we regularly run into Ubuntu and Debian based Atlassian systems. I know of a couple of Arch and Gentoo…
-
Argh, fielditis - you've created a pointlessly unwieldy and probably utterly useless system for your users. Jira is not designed for this, so, no, you can't stop it moving the dates into the date section.
-
Stop using SQL, it's the worst possible way to report anything in Jira. For a start, you do not understand the structure of the data or tables, and I'm not sure about your SQL either, as the last line is nonsense. But, if you must, then you need to explain the actual question: It's clear you want all issues that match a…
-
You are looking in the right place, a report add-on that enables ok, but does not insert a report in the list usually has a broken atlassian-plugin.xml. Can't tell you much more without seeing it!
-
If you use "restore backup", then it will clean out your existing Jira before importing. If you use "project import", that will import a single project. You will need to configure the empty project, ready to receive the issues from the backup
-
If you can still log in from the server on localhost:8080, then we know it's running. This means there is something on the network blocking access on 10.2.34.77 or that the address is incorrect.
-
Tempo is a global add-on. The closest you'll be able to get is by setting up groups and teams such that the ones working only in certain projects don't get Tempo functions.
-
Are your Jira and Confluence systems running on a Linux box? We've recently seen Atlassian applications do this when the Linux distributions have stopped providing the fonts they ask for. Have a rummage through the logs for the word "font" and see if there are warnings about missing ones, or using alternates. Those errors…
-
Correct, that answer was incorrect, there is no option to stop a full index run. You have to stop Jira
-
What about using the right REST call?
-
There is definitely something odd going on, as the links on that page are coming up incorrect.
-
Ah, "site admin" implies Cloud, where you don't have the right to change some global permissions. I don't think you can change this on Cloud, so the closest you can get is to remove "confluence user" from all space permissions and use your other groups separately
-
Your licence entitles you to use any version of Jira released before the end of the licence, so there's no additional upgrade costs if you have a current licence. For Jira Software (which is what you need to go to as you have the Agile add-on which goes away in version 7), see…
-
Could you try another browser? Also, can you read the logs to see if anything goes into them when you click?
-
Yes, by creating add-ons for the blueprints. You'll need to do some coding, and https://developer.atlassian.com/server/confluence/confluence-blueprints/ is a good place to start reading