Comments
-
I'm still not seeing which document you are reading.
-
Sounds like you need lots of boards. Remember that a board is not a container for issues, it selects the issues you want to include. The issues are the things you will be working on. So for each board, you should select the issues relevant to that board. If you want to have a board represent a mix of others, then give it a…
-
No. I give them read-only access. Then they can see that they can trust my reports, and go and build their own, saving me time. And get involved in the collaboration if I let them have some more rights. It's a far better model, to work with your clients.
-
There's a few things you might mean here, could you tell us what documentation you're reading?
-
If a user can't see the information on which you are basing reports, then they can't have any faith in your reporting. This has always been a massive problem with project server and taiga where I've run into them - "trust me and my reporting, but no, we're not letting you see what we're basing them on or how they are…
-
JIRA or Trello?
-
Have you looked through the blog post Ivan gave?
-
Yes, I wouldn't build and tear down instances. I'd get a set that work and reuse them. Or even one shared instance. No need to keep relicencing, and it won't repeatedly cost you a lot more money.
-
Ah, so you've got an add-on that does some of the work. I'm not familiar with that one, but no, I don't know of anything that will do this.
-
The best practice for this upgrade is to do an in-place upgrade. Probably on a copy of the 6.4.12 copied over to the new server. 6.4.12 to 7.3.3 is probably going to work ok, but you will need to test it thoroughly, as it's not guaranteed. Any problems, then go to 7.0 first, then up to 7.3
-
It depends partly on how you are doing this "auto provisioning". If you're running the installers, part of the setup will need you to have some script that can log into your my.atlassian account and buy another licence. If you want to do it without the installers, you'll need a web-script that can do much the same but then…
-
No. You were clear. An Atlassian server licence is for one year. There is no "cancel", and there is no "automatic renew". You can get a refund in some cases, but they're not going to repeatedly refund you.
-
There is no automation available for that. You could probably automate the buy of an annual licence, but the refund process usually takes some human intervention and Atlassian won't do it repeatedly. Your "cancel" is not going to work.
-
Default Custom Field Manager was deprecated a long time ago, and removed from version 7. Try customFieldManager.getCustomFieldObjects(issue) instead.
-
It is possible to automate the deployment of licences with some fiddling. But you're going to have to buy a new licence for each instance.
-
Absolutely. Neither Cloud nor Server stop you from having people in different organisations accessing the system. It is however, quitely likely that your network will be stopping external people using your JIRA if you're running a server behind a standard firewall. It's more of a networking question to get people access to…
-
Yes. Give them access to the space as usual, by giving their accounts or groups access in the space permissions. Then make sure they do not get access to the other spaces. A common default is to have the "confluence users" group represent "these people can log in", as well as provide access to spaces. That will need to be…
-
JIRA hides fields that do not have any data in them, to reduce screen clutter. Most custom fields support a default selection though, so if you put that in, you should find your users will generally put something in. That's in the custom field configuration. (The other option is to force empty fields to show, which looks…
-
Natively, you can't. "Create issue" allows a user to create any type of issue in a project. There are some tricks, including * Javascript (clunky, hard to write, hard to maintain, and a doddle to get past) * Injected javascript by add-ons, such as the Behaviours module in ScriptRunner. (Yes, I work for Adaptavist, but…
-
Yes, I know. It's instinctive to humans, but a ranking field is technically quite hard to implement. If you want a bit more on why, then there's some stuff about it on Atlassian's site that discusses the JIRA Software implementation of the "Lexorank" stuff they did for it. There was a ranking field before they moved it to…
-
Software and Service Desk may not be upgraded automatically, it depends on the version compatibilities.
-
No. The system add-ons are all "type 1" or "type 2" plugins. The "system" flag is set to indicate that the add-on is part of the core product and should generally not be disabled. You cannot deploy that type of add-on on Cloud. The only add-ons you can deploy on Cloud are the approved list Atlassian exposes in your…
-
Ah, that old chestnut. There's a horrid bug in JIRA that hasn't been stomped on for years. When you have a step with no outgoing transitions, you can't add one while it draft mode. You will need to copy the workflow. Edit the copy, adding the transition, then create a new workflow-scheme (I would copy the existing one for…
-
No. A server add-on is a totally different thing to a Cloud Connect add-on. You might be able to reuse some code or logic, but the frameworks are totally different. A Server add-on runs inside JIRA, a Connect add-on is a web-application.
-
Ok, to get an issue out of your "archived" status, you need to have a transition out of it in the workflow, and have permission to use it. It's hard to see from that diagram if there is an outgoing transition. You'll need to get one of your administrators to edit the workflow - first to see if there is a transition (and…
-
Try "Epic Link" = SPA-4 or "Epic Link" = SPA-5
-
Correct. It doesn't need it, as there's no ownership of schemes.
-
You can apply it on any transition you want. Most would put it on Create because they want to hide the issue for its whole lifecycle, but for your workflow, I would consider doing it on activate. The users would then see that they've created an issue and everyone can see it, but as soon as you activate it, it would…
-
JIRA doesn't have field level security, and neither does Service Desk. If however, Reporter A is only a customer and not a full JIRA user, then Service Desk will do this if you don't put the field on the portal. A will only see the portal, without the field, but B will have access to the issue behind it, with the field on…
-
That is the correct behaviour. Your administrators need to be able to administrate the system, and that means having access to change all the config. They don't "own" parts of the system, they have access to all of it. You won't be able to do this with an add-on, and certainly not with a simple couple of class calls.…