Comments
-
Have a look at one of these "closed" issues. Were they in the far right hand column of the board when the sprint was closed (look at the status at the time of closing and the board column mapping). Also, did they have one or more sub-tasks? If they do have sub-tasks, check the same for the sub-tasks - were they in the…
-
No. The whole point of a status is that you can point at an issue and say "The issue is in this status" For Billing and Training, there are a couple of options - the simple one is to have fields that cover it. But you could also create sub-tasks for Billing and Training, and they can follow their own independent lifecycle.…
-
That sounds right - all in the Admin UI right?
-
2) Good, we can forget that line of thought1) Not what I meant (although it may also be useful). Go to Admin, hit search and look for "log", you should find an audit log mentioned. Enable that.Although your debug line might be quite handy too - next time the resolutions go missing, have a look at the application log - the…
-
Ok, two follow up questions1) Can you enable the admininstration log and then see what it says the next time the resolutions are re-added? 2) How are you deleting the resolutions?
-
I've seen this happen with addons as well - some demand certain resolutions are present and if they detect they're missing, will add them in even if you delete them. What are the four resolutions that keep being re-added?
-
It thinks it's spotted a reference to a Jira issue in the repository and is asking you if you want to create it.
-
I don't know how else to phrase it. Copy the key from your my.atlassian site, go to Jira -> Admin -> licence and paste it into the big empty text box that says "licence key"
-
Ok, so you have a valid licence on the Atlassian site. What *exactly* happens when you paste it into the licence screen in JIRA?
-
What does "it didn't work" mean? If it's the same error, then you have NOT been renewing your licences at all, you've not been paying for them (or you have another account and you're looking in the wrong place). Check the dates displayed on the my.atlassian licence pages.If it's not the date error, then what is the error?
-
Ah, ok, well, the error messages tell you what is wrong.The licence you have installed is invalid for the version of Jira you have. You can only upgrade JIRA to a version that was released BEFORE the end of your licence.Now, you say you've been paying for the maintenance for 100 users. That's fine. But I suspect that you…
-
Possibly. Check the end date on your licence in JIRA carefully - what exactly does it say? For your questions * Maybe * No, it changed between 3 and 4, but not again * No.
-
You don't. You can change the logos within the applications, but this screen is a shared resource across many applications and can't be customised by the end user.
-
Set up two "field configuration schemes" - one with component mandatory, and the other with it optional.
-
Hard to work with no description, no symptoms and not even a link to the bug report. And the bug report doesn't have anything more than an error report and a comment that support fixed it. I'd raise this with https://support.atlassian.com - there's not enough information here for us to help
-
There doesn't seem to be anything wrong there. And what "answer"?
-
What answer?
-
Of course you can see all the processes on one board - you add the columns you need and map the workflow status into them. What you're asking for is for groups of columns, which Jira Agile does not do. It has a basic group for "new", "in progress" and "done", which is a standard for both Scrum and Kanban, but no sub-groups…
-
Hmm, that's an odd approach, you might as well throw away the boards if you're going to do it that way, as you probably should be doing the processes separately for each type of issue.Jira Agile won't do this. A column is a column, that's it. A column represents a collection of status (often just one). The closest you can…
-
I don't think it is clear what you are looking for here. Each column in a Kanban (or Scrum) board represents a step in the process (or processes) that your issues are following. Even when you've got the more complicated scenario where you have your workflows representing different processes for different issue…
-
Exactly. There's no way of knowing exactly why there is a memory issue until you can get it running and examine the java process memory usage. But the log is 100% clear - it hasn't got enough memory and it needs more.
-
I'm afraid the log is telling you what is wrong - it has not got enough memory. As Fabio says, you need to increase it. It doesn't matter that "it should not be the error", the fact is that it is.
-
There's two possibly unrelated questions here. To change collation, the easiest method is often to export the system to XML, create a new database with the right collation settings and import the XML. Some database servers will let you do it with SQL as well. In both cases though, if you have data with the incorrect…
-
Absolutely - as long as the application server can run Java, Jira will be fine. Personally, I'd strongly advise sticking with PostGres over SQL-Server, but that's just because of a string of really bad experiences with MS-SQL (heck, it's so bad, I'm actually pleased to migrate people to Oracle!). That said, SQL Server 2008…
-
Ahh! So the upm was being broken by a broken proxy! Very well spotted, I'd have struggled to find that.
-
Ok, it's not what I ran into; there's a -D flag you can set that removes the "upload addon" function. I'm afraid I have to go back to "your UPM is broken". You've ruled out all the possible ways to disable the upload addon function, and there's nothing in the log, so I don't know what's wrong. All I can think of to do next…
-
Oh, one other thing that I didn't know until I ran into it a minute ago. Could you have a look at your system information page and find the JVM input argument settings? It might be called something different on your system, depending on version, so here's the first couple of lines from the JIRA I'm looking at today - lots…
-
Your UPM appears to be broken. I think you'll need to fix that first! Have a look through the logs to see if there are errors in there to begin with.
-
To check the modules, go to manage add-ons, find the upm and look to the right, it will say X modules of Y enabled (for most add-ons, X = Y, but not always). Have a look at any disabled ones. I really don't know how to get rid of "upload add-on" though, except by being on Cloud.
-
Ok, that's good (I had feared you were using a Cloud download, which would kill the upload option) But it does leave me a bit stuck - I don't know how to disable the upload function cleanly without causing errors that you'd see in the logs, except by logging in as a non-system admin. Disabling the whole UPM will do it, but…