Comments
-
When all the stories are done.
-
Start by simplifying the board filter. Drop the "status in" clause to begin with and then refresh the config. Are you 100% sure that all the projects that are "not in (xxx, yyy, zzz)" are using workflows that include the "In QA review" status?
-
Like this: https://confluence.atlassian.com/display/JIRA/Current+Reporter+Browse+Project+Permission I don't know if you can do it on OnDemand (but you've got Atlassian in your name, so you should know this already)
-
Sorry, I wasn't clear. They won't stop you doing it (without code), but they highlight the column has a problem by going very red.
-
Remember that only project admins can set constraints, they're useless if the ordinary users can botch them to suit themselves. The standard documentation is far better written that anything I'd write. See https://confluence.atlassian.com/display/AGILE/Configuring+Columns The constraints really are (deliberately and…
-
No. I have seen the constraints work for "in progress". I have never had a problem adding lots of new issues into a "new" column or moving lots of issues into a "done" column. The docs imply that it's only in-progress that's affected. I just haven't tested it with constraints in mind. "entirely on speculation" isn't quite…
-
No, for exactly the reasons you state - not allowing "new" issues would be a bit of a bust. Equally, would you really want to limit what you can move into "done", just because you set a limit? I have not actually experimented with this, but the docs (and, common sense!) strongly imply that column limits only apply to "in…
-
They prevent cards being dragged into the column when it's going to overflow. Let's say you're using story points and you set a limit of 10. You've got a pile of cards, all with story points set to 3 - you can drag the first three into the limited column, but not the fourth because that would take the total from 9 to 12.
-
I don't know. If you can do it, it's javascript (which can be bypassed, is usually inadequate because it only covers some of the usage scenarios, and almost always goes wrong during upgrades), but I don't know if you can inject any into service desk
-
You can't do it by request types (they're supposed to be simplified and consistent for users).
-
I'm not sure what you are looking for in terms of "demand management", or how you'd apply it to user groups? Could you explain a bit more please?
-
<sigh> Read https://confluence.atlassian.com/display/JIRA/Managing+Project+Permissions The steps you are asking for are on there, under the headings * Creating a Permission Scheme * Associating a Permission Scheme with a Project As it say, you will need to do the second step for each project
-
Add the schemes you need, go to the project as an admin, and select the scheme you need in the project settings. I'm not sure three is more to it than that, and the docs do cover that.
-
That question is like ringing a car mechanic and telling them "I can't drive home", then expecting them to help you without knowing if you're in a ditch, out of petrol, been attacked by a horde of penguins, or even near the car! What does your log file say? What are you running? What settings have you tried? What have you…
-
It usually means the proxy settings you have for the route to Confluence are incorrect.
-
Most things that happen to issues fire an "event". JIRA uses these internally for some things (most notably the email notifications). As you've already noticed, post-functions only work on workflows and there's not really a hook for non-workflow actions. But the actions still fire events, and you can write listeners to…
-
Depends on how you use "fix version" - some people use it for "this was fixed in" and others "we aim to fix this in". Both approaches have advantages and disadvantages. Some teams would benefit from a third "target version" as well. If you do, then I recommend that you use "fix version" to say "this was fixed in" and…
-
I think the nulls are when someone has allowed anonymous access and someone has commented without needing to log in. But I'm not sure. I'm really not sure where it might be getting those comments from though. Oops - a thought, do you use time tracking? I just had a sudden thought that maybe they've logged time with a…
-
Bother, I was afraid of that. Your database is ok, but I suspect your index is not. Is it possible to schedule a full re-index? The one that locks the users out and rebuilds the whole lot from scratch? As there's no broken-robert in the database, it sounds like the "can I kill the user" check is running into a hanging…
-
Ah, right, yes, that could be "fun" I think your best bet is exactly what you thought - SQL. As it's just a comment, it's not easy in the UI, but the comments are reasonably easy. Select * from jiraaction where author = 'brokenuser' ; That should give you an issueid to refer to in jiraissue, and hence you'll be able to…
-
Rename one of them with something obvious in the display name, then you'll be able to see the difference
-
There are 18 different places you will need to check and possibly update with SQL. Remember that you'll need Jira offline and backed up before you toouch the database. If you're potentially working in financial systems in the EU, you should to check with your financial regulator body to check that destroying tracking…
-
You don't even need to "deactivate" them. Remove them from all groups and roles, change their email address to a dummy one, and that will prevent all of the problems above (including the massive one that deleting users who have done stuff in your system destroys information and hence you really shouldn't be deleting them…
-
Ah, ok, the other day I ran into this again, and I need to change my stock response. In Jira 6.1, Atlassian have fixed a bug. Before 6.1, only reporter or assignee would block removal of a user. That has now been extended to include users who have commented on an issue. So, now, I'm afraid you only have three options: * Do…
-
You delete them It's only assignee, reporter and project lead that prevents deletion of a user. Reassign the issues, change the reporter and remove the users from project leads and you're good to delete them. Of course, there's consequent damage to your issue history (comments etc) because you've only got a login string…
-
Um, this is a general forum for all users. You need to address this to the author of the plugin you are talking about (I assume it's https://plugins.atlassian.com/583856 ?). I'm not saying it's wrong to ask about it here, but you are relying on the author reading this specific post - there are a few hundred a day and…
-
No, because numbers, by their definition, do not have leading zeroes. A number padded with unnecessary zeroes is a string. (How would a compute know how many zeroes to pad any given number with? Do you pad numbers with 0's in real life?) You do have options though - find or write a field that holds numbers, but displays…
-
You don't. That change requires code change, which you can't upload on to Cloud.
-
The import thinks in milliseconds, so you're importing a few seconds, which JIRA rounds up to 1 minute. Try 3,600,000
-
There is no way you can do this, as Boris first said. An issue belongs to a single project. Sub-tasks have a single parent issue and hence have to be in the same project as their parent. Links are there for representing cross-project relationships. You either need to move your users into the same project, or use links to…