Comments
-
The software is covered by the licence. The physical costs of humans doing the upgrade are not. You'll need to look at that. Personally, I'd be looking at getting a proper provider on-board, one that is Atlassian-familiar and offers regular upgrades as part of the package.
-
id is the unique id for the line in the database representing a user. It is NOT the user's login. Try using lower_user_name instead of id.
-
That suggests either an installation that was for one of the supported databases, or a damaged install that the database driver has been rendered unusable. Corrupt files, incorrect permissions or virus checkers can all kill the access to the driver. The usual culprit is permissions, but you should also disable anti-virus…
-
I would very strongly recommend 6.4 > 7.0, not 7.5 - there are known issues jumping from 6.4 to 7.1 or above
-
You can't change it. In theory, Atlassian support could, but they don't, because it is there to stop you crippling the system with large downloads. What are you trying to achieve here? Not the download, but what information are you looking for?
-
No, not the export, the xml backup of your whole system. It is still going to take you a lot longer to deal with than examining the reasons you think you want a functionally useless 20k download.
-
Without any coding, three options: 1. Map your teams as Project Categories, then use filters like "category = Team Yay" 2. For each team, have a different workflow with a post function on "create" that sets the team data somehow 3. Set up components and a dummy team lead and auto assign to them (this is easy to set up, but…
-
If a user has permission to edit templates, then they can edit all of them
-
Ok, you'll need to explain more about "I can't get in". However, I suspect you need to talk to your Jira admins first. We're a community of end-users who don't have access to your Jira.
-
Sprints do not belong to projects, they belong to boards. If your board happens to include several projects, then there's still only one sprint there, so when you change it, of course it "changes in the other projects" - there's one single sprint.
-
See https://confluence.atlassian.com/doc/server-hardware-requirements-guide-30736403.html and https://confluence.atlassian.com/enterprise/jira-sizing-guide-461504623.html If you're running them on the same server, then, in terms of memory, you can simply add the two requirements together (e.g. if the guide says 2Gb for…
-
You can renew from your my.atlassian account used to purchase the originals. Annual maintenance is half the price of a new licence. For "Best Price", some partners and resellers are able to offer small discounts.
-
That suggests you have renewed your licence, but not applied the new key to Confluence. Your account knows about the new licence, but you have not told Confluence you have it.
-
Yes.
-
Before anyone asks why she looks small, evil and a bit scraggy, she is * the runt of a litter who was starved as a kitten before being rescued. * a pure black cat who is well over 17 (90ish in human) and hence allowed a few white hairs. * evil.
-
Esk got a round of applause at Summit:
-
Ok, the JQL it is using is simple - it's the board filter, with "sprint = <sprint you are looking at>" added to it. I suspect you're looking for something more than that, but I cannot work out what you're aiming for?
-
Without knowledge of your network, there's no way to guide you. You'll need to talk to your network admins.
-
It's called "time tracking" in the list of fields available for screens.
-
I don't feel so bad for stealing your "don't allow delete" paragraph now. :-)
-
That sounds like the database is set up incorrectly for Crowd. I suspect you have the "strict trans tables" flag on.
-
Well, you appear to be using a document for a different version of Jira, but this error is not caused there. "no privileges on tablespace 'USERS'" is very clear - your Jira database user does not have the right to insert data. Check that you are pointing the system at the right database inside the Oracle installation, and…
-
You need "transition issue" permission to perform any transition, so you need to grant that to all your users. You can limit who can do things in transitions with "conditions". There is probably a condition on your "resolve" transition that says "only people with resolve issue permission". You should probably add other…
-
Because there is something stopping it from being in your backlog. I think we need to see your filter for the board, then a screen shot of the issue details, and maybe the column definitions for the board.
-
Yes, there's something already running on the server on that port. Try running "netstat -plant | grep 8090" to see what it is.
-
Then you need to work out why the issue is not in the backlog. Could you look at the filter for the board? That should tell you why your issue is not included.
-
Create a new scrum board, and make sure it includes the issues you need to add to the sprint. You can have multiple boards looking at a project, but the project will default to showing you the last one you used. You can kill off the old Kanban board if you don't need it.
-
No, it doesn't. It says resolutionDate is an alias for resolved, which is a word you use in searches, not really a field. I was not clear in my answer that I was talking about fields. You can use resolved and resolution date interchangeably in searches, even though it's not quite a real field and the data it searches on is…
-
Project type is Business, Software or Service Desk. You can use either type of board with any type of project, and have as many boards as you need
-
Ok, I'd create a scripted field that calculates the difference between the date and time fields "created" and "resolutionDate"