Comments
-
It means it is one single application. When you install Confluence, you get Confluence. JIRA is a Core application with the option of adding other applications (currently only 2 - Service Desk and Software). So a JIRA installation can be between one and three applications, which is why it needs to handle application access.
-
Confluence is a single application, so it doesn't need "application access". You add users to one of the groups you have flagged for "can use" permission (see admin -> global permissions, and note that although the default is just "confluence users", you can add other groups) and they have access. You can't add individual…
-
No. Not migrate. They will be upgraded to 7. Assuming you use JIRA Software.
-
They're on Cloud, so no, they can't.
-
No. A transition can only have one end point. If you were not on cloud, you could do some stuff with auto-transition scripts or listeners, but those options aren't enabled on Cloud
-
Ah, sorry, I've been completely missing the question. You can only install a certain set of "type 2" add-ons in Cloud. The list of those is short, totally determined by Atlassian, and you do it by enabling them in your account, not via the UPM (It's the Cloud options for Tempo, JIRA Suite Utilities, Toolkit and so-on). You…
-
I'm not sure why you keep asking about "connectors". Cloud lets you install Connect add-ons, some of which are hosted entirely on there, others hosted on other servers. It does not let you install "type 2" add-ons/ Menu items are done in similar ways in both types of add-on - as "web items". On the Connect side, try…
-
Sorry, I'm not talking about "connectors" - those are just one thing you can do with add-ons. If you write a Cloud add-on that runs on another server, then you need to provide that server. There are Connect add-ons that run entirely within JIRA and don't need other servers, but you've written one that needs external…
-
No, it's a good place to ask, it's certainly related! The answer is maybe - Connect add-ons can add things to the UI, but they can't get into the depths of JIRA like type-2 add-ons. Everything they do has to be on the surface and act via REST. Specifically for adding links in the UI, I don't actually know - I've not tried…
-
I'm not sure they're "disguising" anything. If you want to extend or customise Cloud beyond the options in the basic offering (and limited range of options), you need to do it with Connect add-ons - they've said that from day one of Cloud. Sadly, despite "Connect being the way forward", it's not available for Server…
-
That's going to be impossible to tell - Atlassian might be able to give you some numbers based on their licenses but it's not going to tell you what is out there in the wild. I'm still working with large corporates using Jira 3, having no resource (or in one case, desire) to upgrade. However, I wouldn't bother with coding…
-
Go for the latest version of JIRA The easiest option is to install the "JIRA Subversion" plugin - that provides a simple "Subversion commits" tab on each issue. It's basic and read-only, but won't stop you using fish-eye as well.
-
No, you can't, Cloud urls have to end with atlassian.net at the moment.
-
For all of this, look at the transition the developer uses for "sets the status to resolved" - that's part of your workflow. First, you need to think about how you get the "tester" in there. Have you logged this in a custom user picker field? If so, you can use one of the "copy field" workflow post-functions provided by…
-
Sorry, the ADMIN header - that always displays Category: Value (value being "none" when it's not set)
-
Go to the project header and click on the category at the top of the page (you have to be an admin to do this)
-
No, not without code.
-
You can do this in version 6 of Jira. I don't think it's available in 5.x without a bit of coding.
-
You really should step through the versions I've already mentioned. You can't go direct, the documentation is clear on that.
-
There's not a lot of information here to tell you what specific risks you might have. Please have a read through https://confluence.atlassian.com/display/JIRA/Upgrading+JIRA to start with and see if there's anything in there that you don't understand or highlights any concerns about your setup. The only question I can…
-
It will only apply to issues that go through the transition you put the post-function on. But that's what you want to do anyway, from what you've said.
-
Definitely a case for "set the business unit field depending on the user", rather than try to bludgen the user into it.
-
Gabrielle has the right answer to "limit the ability", but it's a really ugly idea. User goes in to create issue, fills in a load of data, gets told they can't create the issue and that their way of logging it is "wrong". It's extremely frustrating to have that done. A far better way to do it is to not offer the user the…
-
Notice the errors "the value X does not exist for the field project" - it's trying not to give away that there is a project there with that code to people who can't see it.
-
You will need to write code that can add web-panels to the issue view. That mostly means writing add-ons for JIRA.
-
Most of the Atlassian Partners would probably be happy to undertake this work, but most of them don't scan "Answers" looking for requests like this. You would be better off asking them directly - see https://www.atlassian.com/resources/experts
-
I'm afraid there is no such method. JIRA permissions are permissive and additive - you give people the ability to do stuff, and they then can. Not give them and take away later. Issue Security is the exception there, as it can hide individual issues from users you've previously granted browse permission to, but it is issue…
-
In the project you want to protect, you need to change the membership such that the people in your "black list" do not get access. Take the example of "create". The permission scheme probably says something like "Create: role: users", and then you have the group jira-users in the role of users in the project. You need to…
-
The ability to edit the due date is controlled by the permissions - the user must have "schedule" permission to be able to set it. I suspect your normal users don't have "schedule" and your developers do. The list of fields restricted this way is mercifully short (although there's a very popular request to be able to do it…
-
You can't. There's no bulk-download. I'd script a REST hit on them all, or better yet, try Bob Swift's CLI to get them.