Comments
-
Not unless you've got a really low amount of resources on the server running Confluence. 6,000 pages is something we'd class as "tiny"
-
The label field proposes existing labels when a user starts typing, and if they don't like any of the existing ones, lets them add a new label.
-
You'll need to write some code to do that. A post function could catch the update and check values. However, an more simple solution would be to just use a labels field.
-
You could do this with the Behaviours module in ScriptRunner. (As an aside, I'm not sure why this is of any possible use when you've got the version already. There's no need to duplicate it)
-
Check the conditions on the transitions, and that you have the permission to perform them (including "transition issue" - I suspect that's what went wrong with Rob's setup above.
-
Look at the "workflow scheme" for the project. This maps workflow on to different issue types for the project you use it in
-
That suggests it may be language specific. Could you translate the red box for us?
-
Yes, pass in a list of Options. The array you're seeing in the error message is not a representation of list of options, it's a string. So you're not doing what you claim there. The fact you're talking about length of the string tells me you're not passing options. Could you give us the actual code?
-
Again, there is no Cloud licence. You'll need evaluation Yes, upgrade from 5.5 to 5.13, then 6. If you have never done an upgrade before, I would also recommend that you go to Confluence 6.0 before 6.latest. Once you're on the latest Confluence, yes, follow…
-
Request participant is not a Core Jira field, it's a field for requests in Jira Service Desk. It therefore can't be used in permission schemes. You might be able to work around this with a custom multi-user-picker field into which you copy participants with ScriptRunner or Automation, and use that in the permissions, but…
-
There are two things here * You only burn down on story completion, as it's the stories you committed to do in the sprint * Time logs for the sub-task belong to the sub-task, not the story. You need to log against the story if you want to burn down on time logs
-
No. You don't get a licence for Cloud, you get access to a service run for you. You need to get a new licence from my.atlassian.com
-
The issues all retain their global rank. If they were ranked below issues that you've moved into the new sprint before closing the old one, then you'll find they come in lower than those.
-
That is not the edit screen, it's log work. Please have a look at the edit screen, by clicking "edit" on the main issue view.
-
Run a search for the issues you want to report on, then save it with a sensible name, and then use it in dashboard gadgets. A simple gadget for "filter statistics" will give you the basics. In the config for that, select your saved filter, then "assignee" as the statistic. That will show you number of assigned issues per…
-
You can't export more than 1,000 issues because the system is locked down to prevent you "denial of service" attacking it with downloads. Going over 1000 can render a Jira unusable for others. Vasiliy has given you the right doc for multiple exports over 1,000 issues.
-
I've edited some personal stuff from your answer to prevent spam and misuse. Yes, you need to upgrade to 6.latest first. I would strongly recommend going to version 5.13 and then to 6.latest. You will need a new licence to upgrade, but as you are moving to Cloud, you may be able to do this with an evaluation licence.
-
The bulk of people here are English speakers, the error messages you have can only be read by a small minority of people here, so you have quite a limited audience. Could you either translate them into English (the contents of the red and yellow boxes only), or, better, temporarily change your profile to English, replicate…
-
It sounds like you added the field (it's "Time Tracking" on the list of fields in the screen config screens) to the Create screen, but not the Edit screen. Make sure it's on the Edit screen as well, then use Edit - you should find it appears there and you can enter data for it on the older issues.
-
Are you on Cloud systems here?
-
No, the user experience does not suffer. In fact, having too many admins is pretty much at the top of the list of things you never do in Jira, and you should ensure that your admins are either experienced, or cautious, disallowing change until they know how to support it. The right to change workflow is complex across the…
-
How far through "configuration" have you got?
-
The project types are Business, Software and Service Desk, reflecting a set of templates for each of the three Jira applications (Core, Software and Service Desk) There isn't any further categorisation you can do. Although if you're willing to code, you can write your own project templates and drop them into one of those…
-
I'm afraid there's no way to copy board settings yet (not without add-ons)
-
As I said, it's being rolled out over the next few weeks. Some people still have the option to go back, but it is going away.
-
As an admin, you can add other people to the admin group(s), so you should get them an account and put it in the admin groups. I'd recommend adding them as a technical contact on your my.atlassian account as well, if they need access to licencing or may be needed if your admin groups change.
-
It is not a "beta", it's ready for production, and is being rolled out in full to all Cloud users over the next couple of weeks, no option to go back to the old one. (Note that Atlassian's "ready for production" is not the same as mine. I don't think it's in the slightest bit ready for general use, it fails me in too many…
-
I assume this was your "site admin" then. You'll need to log a call with Atlassian support to get another site admin added.
-
You don't "save a filter to the board", you just change the filter.
-
I'm guessing this is a custom field, so go to Admin -> Custom fields -> <find your field> -> Configure and you'll see the list of options, with buttons for re-arranging, adding, (de)activating and deleting options.