Comments
-
I assume you mean where people have used https://somewhere/in/confluence instead of [Some space:Some Page] for internal links, and that it's purely page links. I'd use Script Runner as a low risk option, but it is one of the few things I've resorted to doing with SQL (normally, that should be avoided like the plague, but…
-
Yes, click "assign to"
-
JIRA is a server application. You can install it on any server you want to as long as it meets the basic prerequisites (powerful enough, can run java, can get to a database server somewhere) I guess by "online" servers, you are talking about Atlassian's Cloud? That just means they're running JIRA servers for their clients.…
-
Confluence doesn't have notification schemes, as it's a lot more simple than JIRA in what it needs to send. It makes a simple flat assumption that if a user is watching a page, they want to know about most updates. There's not a lot more to it I'm afraid!
-
And it's similar for add-ons too - you can download them to your own machine, and upload them onto the firewalled server.
-
They can just enter hours, but the "pretty" display in JIRA will combine them into days and weeks.
-
Pretty much, yes, because it needs to know what you want to count for entry and display. 1h = 60m is pretty much fixed and obvious, but it needs to know how you want to translate days and weeks. For example, if someone puts in 1d, it's rather unlikely that they mean 24h, they probably mean 8h or 7.5h, or even 5h if you do…
-
duplicate of https://answers.atlassian.com/questions/42668537
-
You can't do this on Cloud. You could ask Atlassian support to enable the flag on your instance. Raise it at https://support.atlassian.com (I don't think they'll do it, but it does not harm to ask, and the worst case is a polite "no" from them)
-
Ok, but you still need to debug that script. I don't know about the version compatibility - in 4.4.2 you've got the UPM to check the versions, so start with that. If it says you're on the latest compatible version, then have a look in the script-runner docs for that error. I'd strongly recommend reading the script it is…
-
Ok, let's break this down a bit to be clear about what we're talking about You have a set of errors which may or may not be related to performance, deletions, scripting and so-on. They might be intertwined, they might not. First, performance. Frankly, forget that for now, you can't go digging through performance issues…
-
You've got a groovy script that doesn't work. Nothing to do with the delete, you need to correct the script. Secondly for your old issues - try re-indexing.
-
That doesn't sound right - when you delete an issue, the comments, attachments and history are removed. I'd be strongly rempted to check that and read the logs to see if it's struggling with any part of the deletion. With Jira 4.4.2, older versions of the CLI should work fine if you don't want to use bulk edit. It won't do…
-
Wow, 2011, and even then I said "it was a while ago".I know the SQL we used then is definitely invalid now, the shape of custom fields in the database has changed significantly, so it wouldn't help you now.I'd re-examine the current CSV import, it is better than the old one.
-
Depends on how much of your data you want out. It was a while ago, but all we really did was export the outstanding items and import them from CSV. There was a bit of SQL wizardry to line up a couple of things the CSV import couldn't handle, and then we left the old system read-only as a reference.
-
Yes. I've done it for one client.
-
Ah, ok. I remember breaking it with a custom field plugin once, but it was a while ago :-)
-
Just so we can rule them out - what's the OS, version of Jira and version of Java? Be useful to know what plugins you have too.
-
Ouch, could you not capitalise every word? It makes it VERY hard to read. You need to check your permissions first - do you have all the admin rights? Next, check the list of plugins to see if any are disabled because of loading errors.
-
Project in (project1,project2) AND ( status in (stat1,stat2) OR label = capacity )
-
Yes, I am sorry for that, and I hope you'll accept my apology. I put some of it down to being a naturally grumpy old man, some of it down to being stressed out by a JIRA that just won't import properly for the last three days, and the rest down to seeing that problem so many times (You can probably tell that my 8 year old…
-
Ah, good. I'm just being fussy about the language because people have read "set it to unresolved" and not understood that you need to clear the value. I can name at least three places who have added "unresolved" because they've read "set it to unresolved". "Clear" also helps explain what they see when they have added the…
-
<sigh> That is what I already said. It's nice that you dragged up one of my previous posts from years ago to confirm what I already said.
-
No, they didn't have unresolved on the list. But I understand why you're saying it because you are seeing it. JIRA is coded to display unresolved when the field is empty, and JQL understands unresolved as a key word. Take a look at Admin -> Issues -> Resolution - that's the list of actual resolutions available. In a…
-
I'm not sure that's an answer to the question. The question is about setting the resolution, not limiting what can be chosen. But it's a good follow up if Nick is suffering from an admin being a bit eager with too many resolutions. Also, it's not "set the resolution to unresolved". As we've already said, it's "clear the…
-
You don't. Resolution is a global field, it is always there, even if you hide it. I don't understand what you mean by "resolution field reads the fields that I want it to read" You can set up a custom field as an alternate resolution, but it will not tell JIRA that an issue is resolved or not, JIRA uses the resolution…
-
You need to be looking at the built-in system field called Resolution, not adding new fields. I'm not sure why you are adding transitions either. Look at the existing transitions. When they go into a status you want to be an "end status" (status like done, cancelled, ended, complete, closed etc), then you need to amend…
-
You can hide it in the field configuration. But don't. JIRA Core relies on it as the indicator of whether an issue is open or done with. If you hide it, all the default reporting will show everything as unresolved all the time and you won't get the "this is done" strikethroughs on links.
-
For the resolution, change the workflow so that each transition sets or prompts the user for a transtion, or clears it, as appropriate for the landing status. The dates area is just a collection of the date fields for the issue. If you're using time tracking, another pael will appear in that column when there's data for it…
-
Yes. All you need to do is create a board which includes all the projects (or even parts of projects) that you want to work with. The boards all run off an initial "filter to tell me what issues to look at" The most obvious one is a project filter: "Project = XYZ". But you can easily change that to "Project in (XYX, ABC,…