Comments
-
All of them, technically, but not very well. It's an area Atlassian have been trying to improve recently, but there's a long way to go. Your best bet - use the latest version, it's got the most up-to-date mobile stuff in it.
-
Zezeto already said "disabled in all status", and that's correct. The permission to move issues is based on project and user, not status. I'm not sure that there's a step property to prevent move either (there are properties to prevent comments and edits)
-
One trick might be to limit it - only allow "move" rights to "people who are named in a group custom field in the issues". On issue create, use a post-function to put "jira users" into the field, and on issue close, blank it out (you don't need the group on-screen at all to do this)
-
You add "validators" to the transition (similar to conditions and post-functions). See the manual pages at http://confluence.atlassian.com/display/JIRA/Configuring+Workflow However, I don't know what validators are installed in OnDemand instances, you may find they are too limited to do what you need here.
-
Yes, the base url is just one thing that has to be updated if you move the instance to a new address. That's why you can't change it yourself - you don't have the access to change the other things, and a mismatched base url would break your system.
-
Answers will keep reminding you about open questions until you accept the answer - look for the tick to the left of the avatar picture of the user who answered.
-
As this is not going to meet the standard published rules, you will *definitely* need to talk to Atlassian sales about it to work out if they can accept your application. Try sales at atlassian dot com
-
You've let them in somehow. What EXACTLY do you have for all of the lines on the permissions page?
-
Nope, no issues, really doesn't matter what order you do it in. The only issue is if you do decide to use Jira to provide the Confluence logins after you've been using Confluence for a while - you'll need to import the existing Confluence accounts. Even that's not a huge issue, it's just one extra step.
-
This was asked and answered already at https://answers.atlassian.com/questions/12159021
-
And you can't run Confluence and Jira in the same container.
-
I'm afraid if you're on Cloud, there are none.
-
You'll need to tell us what you mean. There are some addons which do poll functionality - have you read the docs for the one you have chosen?
-
Administator rights allow you to change ownership and delete other people's filters, but I suspect you're looking in the wrong place (because I keep doing it too). It's in the admin section, not "manage filters". See https://confluence.atlassian.com/display/JIRA/Managing+Shared+Filters
-
Oh, and please, never say "resolution status" - it's confusing nonsense in JIRA - do you mean resolution OR status?
-
Status has nothing to do with Resolution. JIRA has no way of knowing that "closed", or "ended" or "fraggle" status means "resolved". It works off the resolution field. If the resolution field is empty, JIRA considers the issue unresolved and displays unresolved on screen. If there is any value in the field, then the issue…
-
To activate these users, you need to make sure they can log in to Jira - that means they must be in a group that allows login (e.g. the default group is "jira users"). If you're not sure what your login group(s) are, go to Admin -> Global permissions and look for the "users" permission. You can then add the four accounts…
-
You can define whatever boards you want. However, a Scrum board already represents a sprint. When you're in plan mode, you have a list of issues. When you start a sprint, the working view, is showing the sprint. If you're talking about a Kanban board, then yes, you can set a board filter for "issues in sprint X", and it…
-
Yes, you can, it will need to change any issue with that type to another type though. To retain full control over it, I would search for "issuetype = <obsolete issue type>" and then group them by project (filter statistics gadget on a dashboard) to see where it will have an effect. Then maybe bulk-change one project at a…
-
Duplicate of HTTP ERROR: 503 Problem accessing /client. Reason: SERVICE_UNAVAILABLE any solution for this?
-
No, the graph you've got there is Issue Burndown chart, where the green line represents the issues being moved into the "done" column. I'm not sure why you've mentioned the rapid board, that's not what we were talking about.
-
It's based on the issues in the "done" column. If your data is correct on the issues, then it might be that your greenhopper task columns are incorrect and you've got closed and/or resolved in the wrong columns.
-
I mean exactly what I say - the users enter data, the report runs, it looks at the data the users put in. The green line has gone up because the data entered shows that you're not resolving stuff in the sprint, or stuff is being added in that balances out the stuff being done. We'd need to see the data you've been putting…
-
Um, no, you shouldn't need any post-functions to get the burndown chart. It's based on the data in the issues, as entered by the users. You *could* modify the data deliberately with post-functions, but you would only do that if the users are not entering it already, or you've got a system where you're logging differently…
-
Scripted fields do not hold data, so there's no history for them. If you want them to have a history, you need to do the logic in a post function or listener and actively store the results in a standard custom field.
-
The logs in /confluence-home/logs
-
You'll need to check your logs to see why it's telling you "anonymous". I would check both the global and space settings though.
-
Er, no, it's telling you that they ARE being viewed by someone. It may be a script, it may be includes from other pages, and so-on. But the statement "even if it is not actually viewed by anyone" is factually incorrect. The logs prove that something is reading it.
-
That means your pages are being read by people who have not logged in. If you wish to force them to log in before reading, remove the anonymous "can use" permission
-
Check the permission scheme for the project you're creating it in.