Comments
-
Jira uses the word "issue" to describe its core reason for existing - issue tracking. Issues are of many types - bugs, risks, issues, stories, epics, tasks, etc. Or even penguins if you decide you have a use for an issue described as a penguin (I'm not kidding - I've seen a zoo inventory system done in Jira. Penguin was a…
-
Ah, ok, you can't customise Cloud to that extent I'm afraid.
-
You can't go back any more.
-
See the comment above yours, it's still true.
-
That url looks like a Confluence url, not Lithium, so I suspect the question is about Confluence really. The error message from nginx is helpful - it's not configured or built to handle files as large as the one you are trying to upload.
-
You can get any issues you want from Kian's download, and from REST (REST is an interface for computers to interact with systems, three is a REST interface built into Jira)
-
Interesting one, but my js knowledge of SR internals is weak. Could you raise it with https://productsupport.adaptavist.com/servicedesk/customer/portal/2/user/login?destination=portal%2F2 ? (They'll ignore it if I do it, they're tired of my whinging)
-
This healthcheck can fail like this when Confluence cannot talk to itself. This is often a proxy thing (users all land on a proxy that expects them to come in from the outside, but the proxy is not configured to accept connections from the confluence server, so it doesn't route back to itself) The most common cause is the…
-
Turn the story into several stories, grouped with links or with an Epic
-
I am sorry, but "rechange preview jira version" makes no sense. My best guess is that you want the old layout back. You cannot do this on Cloud, you would need to move to server.
-
I've seen this done on several servers, and the answer is a very clear "maybe". In a couple of places, the metrics came out at "negligble change", one place took a performance hit of around 30% on page loads, and another one saw a 30% improvement. I think it's important to look at why you're doing it, and most importantly,…
-
There is no merge, as it's quite a horrible thing to code for. Atlassian would need to re-write all of their Cloud based systems (community, docs, developer stuff, marketplace, Cloud etc) to enable one unique ID to be automatically replaced by another when an account is merged. I'm afraid your user needs to throw away one…
-
You could, but it's a hideous way to do it. Reading a single simple issue is 15+ joins to different tables. Please use the method Kian suggests, it's far easier and works. If you don't like it, try REST instead.
-
A post-function is too late, it won't stop the user committing the new issue with the wrong data. (Well, you can, if you deliberately crash the process, but that's a bad bad thing to do, as it loses all the input data and gives the user a crash message) Use a validator - these return either "yes" or "no, and here's an…
-
Do you mean Cloud or Server? They are different products.
-
That is what the answer said.
-
Same answer, there's nothing to "overcome", just use two flows.
-
No. Jira Cloud is a different product to Jira Server. You have no control over the version of Cloud and "7.5 for Cloud" is nonsense, it's not even using the same version scheme. If you want Jira 7.5 of Jira go to the "other versions" link on the Server download page.
-
I am sorry, but your question is borderline nonsense. To clear it up, please explain what you mean by * cloning * depreacated and then * what you are really doing * the versions of the software * the actual errors
-
I do not understand what you are looking at. The Atlassian documentation is a bit fragmented because of the poor use of labels, but once you hit a doc that tries to tell you about fields, it walks you through it. What you appear to be asking for is documentation that is more simple than is feasible. Instead of asking for…
-
There is not a lot more we can do than point you at the Atlassian docs, as they contain step-by-step instructions for doing all of this stuff.
-
Atlassian has tech support, over at https://support.atlassian.com/contact - telephone support is for premium customers only (i.e large enterprises). I'm afraid youtube videos, blogs and most social media tend to be useless because things change faster than they can keep up. Anyway. You have Jira Service desk, so * Go to…
-
Custom fields have not really changed since Jira 2, although the interface has a bit. Most of what you are reading is still valid, but there is so much of it (and Jira's sheer power means it has to be complex), yes, it's daunting and often confusing. Jira is an issue tracker, not a survey machine. It presents your users…
-
The tick mark next to each answer.
-
If your Jira is not responding to you, but is running, then you need to read your logs. I know they're long and dry and dull, and not easy to read or spot where something is going wrong, but there is no other way to know what is going wrong. Please, go back to them and read them. There are errors in them that tell you what…
-
7.0.latest is the best target, yes. After 7.0, take a good look at 7.6 (Enterprise, so it's got long term support), and 7.9 - if your focus is support, choose 7.6, if you want the features in 7.7-7.9, jump to 7.9.latest
-
All updates on this are on the issue Sam linked to. That's also where you should go to vote if you want to (comments here are not going to help the cause, and +1s are a total waste of time)
-
Yes, you can mix, but they will be using two different accounts and urls to do it.
-
Mmm, I don't think this is a Jira question - could you explain what it has to do with Atlassian stuff?
-
You have entered javascript into the description of the field. You need to get into the field and remove it (yet another good reason for not using javascript, I wish Atlassian would fix server so it block it properly, like they have Cloud) While you are on that screen, click the cog for the field above, then right click…