Comments
-
What do you mean by "auto update"? It looks like your administrators have installed a new Jira on the url you are using, so my guess is that they have tried an upgrade and got it wrong.
-
I want to apologise for being a bit blunt, but the grants are mostly irrelevant. You seem to have got them right. However, your systems can't connect to the database. "Cannot connect" is a small step forward as it rules out some stuff, but not a lot. Check the connections and permissions again, there's something missing.
-
Jira Agile only exists for Jira 6 and below, but the docs you are reading are for 7 upwards. Could you check if you are running Jira 6 + Agile, or Jira Software (help -> about, at the top right will tell you if you're not sure)
-
Create transitions that have a "clear resolution field" post function on them.
-
That suggests you have something breaking the way the field works, a javascript hack or a broken behaviour.
-
That field is not a field native to Jira, so it's being provided by an add-on. You should read up on how the add-on works.
-
What does "not allow me to add" mean? No field? Greyed field? You change it, but nothing takes?
-
My best guess is that "inactive" really means "on the view screen, I can not enter a value". This happens when the field is not on the "edit" screen so it cannot be edited. Check what you get when clicking "edit" to pull up all the editable fields.
-
It might be possible to kill it with a property in global configuration -> advanced, or with javascript hacks. Is the properties file still fully read/write by the jira user? I can't think of other ways to remove it.
-
It can't just change like that. You (as in your organisation, not just you) have removed or changed the flag from the properties file and restarted Jira
-
What does the documentation for the add-on providing this say?
-
So you're taking Jira offline "all the time"? That change does indeed work for 6, but the latest version doesn't support it due to changes in the way text fields are being held.
-
Import does not support imports of data from different versions of Jira. 7.9 will refuse to import data from 7.8, let alone 5. If you are talking about database imports (i.e. you point a 7.9 to an older database), then in some cases, it will work. It's not supported, it's not recommended and it certainly won't work for…
-
Atlassian are unlikely to look at this, the problem is installing a database on a server, neither of which they wrote. I may have amended the sources file on my server (I don't think I did, but it is possible). Could you try apt-cache search postgresql If that's a bit long and has loads of hits that don't directly look…
-
If you have "delete work log" permission (whether your own or for everyone's work log - note that those permissions are not the same as "delete"), then there should be a delete option in the menu that appears to the right of each worklog (same menu as the edit option)3
-
Code. You will need to download the code for the gadget, change it, recompile it and upload your new version.
-
Issues belong to projects and are assigned to users. To represent a company ownership as well, you've got some options * Custom fields can be used to hold the data (weakness - they can differ within projects) * You could (ab)use Epics to do it * Install something like pro-fields to put a "company" field on the project…
-
Part of the reason for not rolling up estimates in Scrum is the binary nature of the delivery. You go into a sprint announcing that you are going to deliver a set of stories for the product owner/stakeholders. There is no try, a story is delivered or it is not. So the points on the sub-task are an irrelevance, they don't…
-
Slows stuff down when you have a medium or larger Confluence.
-
When an apt-command fails, it can leave the package database in a funny place, where the next apt-command will try to continue where the last one left off. So, if you've just failed to install MySQL, and you run apt-get install postgres-9.6, then apt may well report trying to do things with MySQL. You've got absolutely the…
-
An old Adaptavist one from before Marketplace existed - it was the Plugin Licence Manager. You shouldn't run into it any more (I would check with Jon before saying this as accurate, but I have a feeling the need for it went away when Confluence 4 was released)
-
Short answer is an unreserved yes. Always backup before big change. That said, I rarely do it. I've only seen one add-on break a system badly enough to start considering going to a backup, and we should have caught that well before it was rolled out (the admin did not go through a test cycle, which really would have…
-
Go to the board from which you created the sprint. You'll see the issues grouped into columns. I suspect your "section" means "column", but I am not sure.
-
Basically, that's where I was headed, but wasn't sure! Thanks @Jan-Peter Rusch for picking it up faster than me!
-
The Atlassian one is documented at https://confluence.atlassian.com/doc/viewing-site-statistics-123043962.html (trust it when it tells you it does not scale too well though!)
-
What column were they in on the board when you ended the sprint?
-
Go to the board config and check what it says in the main "general" section where the filter appears. There are two filters, the first is the board filter which selects the issues for display. Check this in the "issue navigator" - does it return the issues you expect? The second filter is basically the "closed" filter.…
-
No, I'm sorry, but in 1, you've done it again. "order swimlanes" does not define what you're asking. 2 makes perfect sense, and is already there.
-
https://confluence.atlassian.com/adminjiraserver072/working-with-workflows-828787890.html tells you about workflows. The section on "workflow designer" has some links you probably want to expand on or follow for more info. A canned version though: * Log in as an admin * Go to the project and find the workflow that needs…
-
But your sort would destroy the ranking, from what I can see. I think you need to explain what you would like to sort. "Swimlanes" is not enough to go on, it needs more explanation.