Comments
-
No, the project level imports are a function of the JIRA importer (system) addons that need JIRA 6.1 or above (I'm hazy on the exact number, but it's not 5.x). You need admin rights to do imports in 5.x
-
Absolutely - I think we drifted off in that direction, and I completely agree that it's totally unclear that you can't add plugins to OnDemand (yet). The docs are good and clear, but obviously not find-able enough. For an API, there is one - OnDemand has the same REST API as exposed in the other options, but that is an…
-
Oops, it won't let me undo my downvote either!
-
No, it doesn't help to downvote a correct answer - it provokes people into downvoting you.
-
Exactly - the fact that it's asked almost every day tells us that there's something very broken in the documentation. As @radm4 points out it's not mentioned during sign-up either, or highlighted anywhere, so people are missing it. That helps explain the volume of questions here. We really need a simple robot that would…
-
("several times" = "several times a day". There's something broken in the documentation or communication around OnDemand policies - people simply aren't aware of it)
-
No. See https://confluence.atlassian.com/display/AOD/Atlassian+OnDemand+Plugin+Policy <sigh. every day someone asks about plugins and ondemand>
-
You will need to write a new "clone" process - the existing one copies an issue as-is.
-
Yes, that would be a simple implementation. I suspect your users would demand you remove it quite quickly though - why should adding or updating a component automatically re-assign something I'm hlaf-way through?
-
You'll need a listener to do the automatic re-assignment on edit. This could be quite hard, as there's no way to know when it's an edit of a clone, or just an edit.
-
You can do this off-the-shelf. Look at the list of components, and you'll find some settings to the right about who the default assignee is - project lead, unassigned, project default or component lead. No need for post-functions.
-
Nope. No change.
-
Correct. Atlassian do keep their logged issues up to date. If that's not resolved, they ain't done it ;-)
-
The difficulty is the definition of "recent". When you ask "changed since", you need to define a rule of the "since". "When I last looked at it" is a start at an answer, but it's a bit woolly as you need to say what counts as a view. Obviously, the full issue view, but then that means you're going to have to visit each…
-
Coding is heavily limited in Cloud - there's no add-ons that I know of that can do conditions coding really.
-
I ask because there's several. Also, ScriptRunner is not (yet) for Cloud, as tagged in the question. Although I should have said that earlier.
-
From which add-on?
-
If you associate different workflows with different issue types, then you can have different validators for them. A validator always checks on a transition though, so if you want one workflow that behaves differently according to issue type, you'll need code, as you'll want to include "check issue type" as part of the…
-
For a small Confluence, I'd enable the analytics which captures the page views. For larger ones, I'd get the Viewtracker add-on (or look at some of the others in the marketplace - I'm not that familiar with them as I've only ever used viewtracker and embedded google analytics).
-
I'd do this with the script runner. Although you'd need something to trigger the scripts at the right times, you can script "project create" and "change permission scheme to a read-only one" for the "close project" bit.
-
Creating projects automatically can be done with scripting or plugins (example - I've just helped set up a "project register" project - user creates an issue in there, a script creates their project for them after a bit of validation). The questions you need to think about are: What is going to trigger the creation of…
-
The greying out of the filter is probably permissions - sounds like the person who set up the board based it on a shared filter that they don't own! As an admin, you can change the ownership of filters, so that might be worth a try. Filters that report projects as id numbers tend to be trying to report on deleted projects…
-
The project the board filter refers to has been deleted or hidden from your account. You should be able to change the filter to refer to valid project(s), but check that you can see the project first.
-
Ok, good start, but there's more. Your screenshots show pherro (I assume that's user who shouldn't be seeing stuff) and their groups. It shows that you are not using any groups pherro is in directly, and that you are mostly using roles to control acces What we don't know is what roles pherro is in, and it leaves us with…
-
What about roles or the other options? I agree with Ahmad here, if you have a user who can see a project, then they have "browse" permission somehow. The usual culprit is the Atlassian default - "jira users" is used to say "people in this group can log in", but then also used to provide access to projects, which you'll…
-
That is right, that is what a cascading select is for, and that's what you've asked for. Choosing a value from list A determines the further options in list B. I don't understand what you're trying to clarify - you've just described exactly what you've got already.Add a custom field, choose cascading-select as the type,…
-
I don't understand why you keep saying a cascading select is a single select. That's clearly wrong.
-
That's wrong. If you have selected "cascading select", then you have a cascading select field.
-
You don't, Confluence permissions are permissive - you allow people do stuff in spaces, not set flags to stop them in general. There's also the layer of page restrictions over the top of that, but they're done by page (and cascade to child pages), not at a top level. You will need to remove whatever is granting your users…
-
I'm glad you finally get the point I made at first - informational IDs are more useful, and abstract ones should be hidden from humans because they're useless.