Comments
-
That's correct - you need to choose to deactivate a person. And if you later decide you want them to create issues again, you'll need to reactivate them. I've scripted stuff that does things like "last login > 3 months ago, deactivate" and "deactivate because an invalid email address means they've left even though HR are…
-
Er, hang on, think this through. A Jira licence seat is taken up by an ACTIVE user. That's what you're paying for - up to 50 people to be active. Either a user is active and uses a licence, or you've made them inactive and they do not. What you're asking for is to have active users who do NOT consume a licence seat. That…
-
Then you should have a update custom field option in post functions
-
There are some addons available in OnDemand that can update custom fields. From memory, the Jira Suite Utilities is available and can do some quite clever stuff with them (not just hard coded value, but "now" in date/time fieds and "current user" in user fields.
-
It's not perfect, the gadget will drop lines where the total count is 0, but you can at least see the low usage ones, and you can use it to compare with the full list of status (if it's not on the gadget, then it's used by 0 issues and can be killed off. Or at least, check the workflow its using!)
-
Right, well, that's "current usage" which is a statistic. The status that a project uses is not necessarily the same as what is currently in use. It's also very easy to get to (unless you do it via the database, where it remains a bit of a pig, albeit a little easier than the original question) Start a new filter, and…
-
We could still help you with statistics, if you could tell us what you actually want.
-
That's not a statistic, that's a configuration thing and it's a one-off. Look at the project's setup to get that, it's easier than trying to read the database.
-
Then you're doing it wrong. You really shouldn't be touching the database. What "statistics" are you trying to get to?
-
Technically, yes, it's all in tables, but it's not a direct relationship and some of the data is stored in blocks, not normalised in any way, so you can't just use SQL to get to it. That brings me back to "why"? What are you trying to achieve here?
-
Two things: * Why? The database is not intended to be used directly, and there is almost certainly a much better way of doing whatever it is you are trying to achieve * If you insist on doing it the hard way, you'll need to read the project config tables for the workflow scheme in use, compare that with the issue type…
-
Which add-on, and how did you install and launch it?
-
The latest. Probably. You'll need to test it for yourself to judge suitability. We can't tell you what you need.
-
You'll need to amend the core code that's doing the page layout and deciding where the panels land.
-
The toolbar in the editor is, well, in the editor. To add something to it, you'll need to rewrite the system add-on that provides the editor.
-
Could you explain what this has to do with Confluence?
-
It's the comment about "anyone". when you add a permission, look for the "group" called "anyone".Recommendation: *NEVER* give "anyone" anything other than "browse" access to projects.
-
Please read the answer and follow-up comments on this question
-
I don't think the fix for the default arrives until 6.3, possibly 6.4! It works by adding an extra permission to the schemes of "can transition issues", so to use it, all you do is NOT grant it to your read-only group!
-
Ok, it's just the move of issues through the workflow that you can do with your read-only user? That's a common oversight by new Jira admins (and it's improved in the latest couple of versions of Jira). You haven't put any "conditions" on the workflow transitions. Jira doesn't do it by default, so admins have to remember…
-
You need to include the group in the permission scheme(s) for the projects too, on the "browse" line. (Or via a role)
-
Sorry, I tend to call it "can log in" because it's more helpful than "can use" or "jira user" Click on the first drop-down and find "Jira Users", and select your "read only" group in the second list, and belt "add"
-
Sort of. The group "read only" is doing what you expect. But it does not grant the right to log into Jira - that is handled by putting people into "Jira users". But, you don't *have* to use "jira users", you can add one or many groups to the "can log in" permission. I suspect the most simple approach for you is to put…
-
It's pretty much the same in version 6 as it is in 5. You need to create a new group then change the permission schemes to grant it "browse project". Start at https://confluence.atlassian.com/display/JIRA/Managing+Users
-
You need to find the "screens" you are using, and add the fields to them. Rather than ramble here, may I point you at https://confluence.atlassian.com/display/JIRA/Configuring+Fields+and+Screens as this can be quite complex and it's got a nice diagram and explanations
-
1. No. Upgrades of plugins are up to Atlassian 2. Atlassian don't publish update/upgrade/release information much, they are more about "when it's ready" than a deadline. If you want information about upgrades to OnDemand, then you need to ask OnDemand support directly, rather than us. But don't expect anything more than…
-
Er, use export and import in the admin sections?
-
No, everything I've done that has been recorded has been via Adaptavist, so you'd have to engage us as trainers to get it.
-
There are some experts who cover Bangalore physically. And a wider range of them who will do online training with you if you want. Have a look at https://www.atlassian.com/resources/experts (Disclaimer, I work for one of the experts. Also, as I type this, I'm supporting one of my colleagues training a group of new admins…
-
Your workflow for the stories has a status called "void", which you have put in the "done" column on the board. Take a look at the issue ITSS-116 in plain JIRA and use the "view workflow" option to see what you've done here.