Comments
-
Even if you fixed the error, it's going to fail - you can not perform a transition on an issue while it is in the middle of another transition. Use a "fast track transition" instead.
-
You don't. Confluence is a rich editor. In theory, you could edit it in a text editor, but you'd have to be someone who can read and write xhtml and be 100% accurate when doing so. I don't think I've ever edited any XML by hand and got it right first time.
-
This was fixed 5 years ago by using the correct username. Another client of ours had usernames with non-Roman characters in them which failed because they had not got the database collation set correctly, so that is worth checking if you are having this problem
-
"Environment was KO" is meaningless, please explain? The link you've given tells you how to set a flag to enable the excel exports. It works fine for me through to Jira 7.11 so you probably want to explain what you've done differently to what the link says.
-
The JQL you are using in the main query looks wrong.
-
Assigning to a group does not work in real life, so Jira does not do it. Service Desk is built for a standard scenario - people raise requests which go in to a pool that one or many teams pull their work from. A person in those teams is expected to pick out the most appropriate thing to work on, and to help them with that,…
-
Whatever Pega is trying to do, it is doing it via "create issue" or "edit issue", and it is using a user account in Jira to do it. You need to make sure that the account Pega is using has the right permissions in the project (create and/or edit, and "edit reporter" too), and that the reporter field is on the screens. Try…
-
In the instance I was thinking of - 40,000 users. But the problem was spam, not the mail handlers themselves.
-
Are you logging in as an admin from the sire you backed up? Your previous account on the target Jira will have been scrubbed by the import.
-
It's on the to-do list. No clear hints of a release yet though, so I wouldn't bet on it before Jira 7.14ish
-
Sadly, no. It's supposed to be an animated Charlie juggling, but sometimes he freezes with different numbers of balls in the air. (R.I.P Charlie, you are missed) If you want to prove your Jira skills over your colleagues, tell them where the Space Invaders/Zelda screens are...
-
See https://confluence.atlassian.com/adminjiraserver079/supported-platforms-950288096.html
-
The standard way to do it is with the commands iptables-save and iptables-restore in the shutdown and startup scripts for the machine, but the package iptables-persistent is a nice wrapper that saves you having to do most of the config for them.
-
I've seen an instance of Jira with over 100 email handlers. It did have a performance issue because of one of them, but once we'd turned it off so Jira was not trying to process 20 spam emails a second, the problem went away. Your performance problems might be down to many email handlers, but there's every chance that it's…
-
Oh, on the passport/travel part, I almost got caught out last year on the way back. I'm Nic. No-one calls me by my real name, including the people who booked my flights. Most native English speakers will make a broadly correct assumption that it's short for some variation of "Nicolas". But not Catalonian airport security.…
-
Ah, good. Yes, you can just download 7.6.7 and install it s per instructions.
-
Install 7.6 on a server, point it at an empty database and allow it to complete a clean fresh install. Then use it. I'm guessing you are asking about downgrading though. This is not possible with Atlassian applications (not without losing a lot of data or spending months doing data transforms)
-
Also, you might want to join it to moved_issues to check for issues that were moved out of the project, rather than deleted.
-
For the background info, the priority icons are additional functionality for priorities. The off-the-shelf custom fields don't have anything that can do it. So you'd need the add-ons Mikael mentions.
-
You're not an admin of Comala in this space.
-
There is no permission for sub-tasks. You can either create issues (including sub-tasks) in the project, or you can not create anything. The only way to remove sub-task creation options is to remove sub-tasks from the project entirely, or remove the right to create issues. The property that prevents all edits on an issue…
-
I don't think it is scaling - when you've got more than a couple of dozen subtasks, it gets too messy for humans. I think you've got the right idea with your moves though.
-
There's not a lot else you can do - Jira is an issue tracker, with sub-tasks intended to split tasks up into more manageable bits. 500 bits is far too many for humans to process as sub-tasks, they would, and should put them into projects, so it's not designed for huge numbers of sub-tasks on single issues.
-
Your 4th user does not appear to be showing as inactive anywhere. I'm not actually sure what the problem is now you know why the first three inactive users are not selectable.
-
>the bamboo IP is automatically resolving to 127.0.0.1 Check that the base url is set correctly (on both sides) and that the network is routing <static-ip> to the right place.
-
You said that already. What you need to do is move up a level. If an issue is looking to have 500 sub-tasks, it's not an issue, it's a project in its own right.
-
You need to read the log files to find out what the errors are. It might be memory related, but I suspect it is something else. We can't really tell you much more than that, you need to read the logs.
-
Sounds like you don't have rights to edit the filter for the board. Try going to the filter and amending it (add "order by rank" clause) and check if you get "save" or "save as" next to the definition. If you get "save as", you don't have rights over the filter, and you'll need to contact the owner.
-
500 subtasks is not an "issue", it's a project in its own right. You should create a project for this "issue", and have 500 tasks within it.
-
What is "label dimension"? A custom label field? What do you mean by "exclude"?