Comments
-
It also sounds like you might not have the right to "browse users" - if you don't have that, users won't be listed in user pickers and you can't search for them - you have to know their user id so you can type the whole thing in. That's a "global" permission, you'll need to check it in the admin section.
-
I read it as "I want to write code that will add columns to the settings", which is one of those actions that upsets users (the nice ones will simply delete it again, the grumpy ones like me will have a go at the admins for interfering with their stuff). I like your answer because the columns should be left up to the users.
-
Yes, you could, but DO NOT DO IT. At best it's a waste of your coding time for almost zero benefit, at worst, it'll just annoy your users. The columns you see are flexible and chosen by the user. There are three places JIRA looks when choosing columns * If the user has viewed a saved filter which has had its layout…
-
Ah, then you need to mark Bob's answer as correct, he beat me to it.
-
What versions of the CLI and JIRA are you using? In Jira, do you have all the remote access enabled? RPC services etc?
-
You've sketched out one way that people do it - a board filter which says "show me issues in status new with field = x, and all issues in other status" Another option is the workflow change - you have a distinct "new" and "to do" status - don't put "new" in the to-do column, people have to accept new items into the backlog…
-
Any that supports standard web services. Not that it matters because you won't be doing any load-balancing, just passing through the connections.
-
Turn off the "Software" application, and the boards will go away.
-
The release notes are often generated after the download is released. The important date is the release date. At least, last time I tested that was the case.
-
All the Atlassian products follow the same licence rules. The answer you got when you asked this about Jira is exactly the same for Bamboo.
-
Ok, Sam's answer is the one you need!
-
This is two separate things. You talk about changing your workflows first, which is fine. But then you describe a problem which has nothing to do with the workflows. Workflows define the possible status for issues. Resolution is separate from that. Changing the workflow for issues will have no effect on the resolution.…
-
See https://marketplace.atlassian.com/plugins/com.radiantminds.roadmaps-jira/cloud/pricing for the pricing
-
It's working as designed - a link between issues is a logical link for humans to follow. It does *not* alter the behaviour of issues. If you need it to alter behaviour, you're going to need a bit of code. The obvious one is to write or find a plugin that will provide a new workflow-condition of "only allow transition if…
-
It's working as designed - a link between issues is a logical link for humans to follow. It does *not* alter the behaviour of issues. If you need it to alter behaviour, you're going to need a bit of code. The obvious one is to write or find a plugin that will provide a new workflow-condition of "only allow transition if…
-
We are not Atlassian support, we're a community of end-users like yourself (although Atlassian do participate, they don't pick up support here). You'll need to contact the adminstrators for your confluence installation, and we have no way of knowing who they are.
-
Not natively, because Jira doesn't do field level security. See jira.atlassian.com/browse/jra-1330 , but also look for the Behaviours plugin which makes setting this up a LOT more easy than writing your own javascript or custom fields https://studio.plugins.atlassian.com/wiki/display/JBHV/JIRA+Behaviours+Plugin
-
I was about to ask for your version of Jira and the Toolkit, but I've just realised you've already given the Jira version. Which doesn't have any valid versions of the Toolkit. I suspect this isn't working because the toolkit plugin simply isn't compatible with your Jira. You'll need to upgrade.
-
That field is a view-only field, it won't do anything if you add it to a create/edit screen (heck, by definition, it simply can't appear on create - there's never anything for it to do on create) You don't need to do anything special - your first three checks are all you need to do. Just put it on the view screen, and edit…
-
This isn't about sending a mail to a group at all (it's got an email address, you can send to that), it's about sending mail based on priority. The situation here hasn't changed - have a look at https://answers.atlassian.com/questions/124458 The code is a little outdated, but the principles are the same.
-
It might help if you told us what the problem is. Restoring to before the update will probably involve going back to the backup you took before you started the upgrade.
-
Cloud or Server?
-
Have you got the global permission to "browse users"?
-
Yes, you can, make sure the "timetracking" field is available in the screens and field configurations for the sub-task issue types. But bear in mind that they don't roll up a lot - Agile almost certainly won't handle them the way you think it will.
-
No, it's not got facilities for that. The best you can do is search for them and scrape the web page that lists the results. For anything more clever, you'll either need to scribble some improved reporting code, or run a quick query in the database.
-
Spot on, to save you having to try it. There's also options with listeners, scripts, automation, but they're all a right fiddle and simply doing it with a post-function or field on the screen is by far the best approach. It's very unusual to set a resolution on issue create, as it means you're creating issues already dealt…
-
Project Lead is not a 'project role', hence Sorin's question!
-
Instead of, or as well as the project lead? Seems like unneccessary work to me.
-
That was another good option - I generally assume that project admins might need to know stuff (especially if the nominated lead is on holiday!)
-
I'm afraid manual work is the answer, as you say, it doesn't have the project-lead option. I'd be tempted to scrape the list-of-projects screen for the names, then add them to a group.