Comments
-
Please see https://www.atlassian.com/software/jira/service-desk/download and maybe "all versions" on there.
-
Rawr. ;-) Jira was written as a direct competitor to "Bugzilla", named after the mis-translation of "Gojira" to "Godzilla". Mike and Scott just nicked the "zilla" bit and spelled it more closely to the Japanese usage (There's no strong Z sound in Japanese).
-
You can't drag issues between swimlanes. The permission to transition issues grants the user the ability to use transitions in the workflow, which are triggered by dragging cards between columns on a board. If a user can't drag an issue from one column to another then the reason is They do not have permission to transition…
-
As above, the answer is "It may be that gmail has been configured not to accept login from there with that user"
-
Scripted fields do not contain data directly, and they cannot be "set". A scripted field works out what data to display, search on and sort by, by using the script associated with it. I don't think you want a post-function here at all. You should take this script and add it to the script for the scripted field, then change…
-
You will need to write some scripts or code to do that. A post-function on the sub-task "done" transition should be able to * read for the parent of the current task * work out from the current sub-task what the next one is * trigger a transition on the other subtask I've done something very similar with Scriptrunner, but…
-
Thanks @Susanne Götz _Tempo_ for the correction - I thought there was some stuff about migrating Tempo between Server and Cloud, although I knew it wasn't fully supported.
-
Ok, a lot of this is good, but slightly confusing and maybe not quite complete. Could you * Give us the main filter definition for the Kanban board * Give us the "closed" sub-filter for the Kanban board. The default is usually something like "fixVersion in unreleasedVersions() OR fixVersion is EMPTY", which is fine, but if…
-
It's one of a standard bookmark - I know the migration process by heart, but I still use it as a checklist (and for answers here, of course. There's often quirks in migration, but if someone is following the guide in this doc, they cannot be far from the right path!)
-
Hmm. Those two look good. Can you show us one of the users with their group (with personal ids scribbled out if you want - we're only interested in memberships), i.e. that they can log in, they're not deactivated and they're in one (or both) of jira-it or jira-head-departments.
-
Nope, that's mostly right. Just missing a pointer to https://confluence.atlassian.com/adminjiraserver/switching-databases-938846867.html in point 1 I think. Point 4 is spot on - always take a backup! But the xml you'll export in order to migrate the database is a backup!
-
I'm afraid the only option is to migrate to Server (either hosted yourself or by a managed service provider) I think there's a couple of good ideas in the new UI, but they're drowned out by the awfulness of the rest.
-
So you need to check the whole chain: * User is active * User is in a certain group * That group is in a certain role (called x) in the project * The project has a permission scheme that says Browse: users in role (x) The permission helper is telling you that at least one of those is missing
-
The main doc on roadmaps at https://confluence.atlassian.com/jirasoftwarecloud/roadmap-957979308.html does no emphasise this well. It does say "Roadmaps are only available in next-gen Jira Software projects, and aren't available in classic projects." in the introduction, but it's not highlighted.
-
Start at https://confluence.atlassian.com/jirakb/migrating-from-jira-server-to-jira-cloud-779160826.html - that will get all your data over, apart from Tempo. For Tempo, have a read through their migration docs (the main migration will take a lot of it, but the change of type of App means some stuff you need to be aware…
-
I understand the symptoms, your writing is perfectly clear. Other web apps are irrelevant to us, if you don't clear the cache, you can't rule that out of being the problem. I am not sure how else to explain "look at the log file for errors at the time at which you try to log out". If there is something going wrong on the…
-
Do not delete users, it destroys referential integrity and your audits. Use the user management to "disable" users instead. These users do not count towards your licence count. You can see the number of "active" users consuming licences in the "manage applications" admin page in Jira and the "licence" page in both Jira and…
-
First hit on any search engine is the standard upgrade documentation you need to start with. https://confluence.atlassian.com/adminjiraserver/upgrading-jira-applications-938846936.html
-
It only applies to "Next Gen" projects
-
Can you find them with a plain issue search, rather than just the boards?
-
Mmm. Not sure that's the problem. What about the issue data? Anything different there (apart from text fields and the issue key of course)
-
There's no way for filters to read each other's settings I'm afraid.
-
My guess is that your project does not have permissions that let you in. Ask your admins to correct the chosen permission scheme or add you to the right roles.
-
Start at https://confluence.atlassian.com/doc/server-hardware-requirements-guide-30736403.html
-
I apologise for my lack of Portugese. There is no way to do this. Roadmaps can only be done in "Next Gen" projects.
-
Not yet, see the earlier question https://community.atlassian.com/t5/Jira-questions/Moving-all-tickets-to-different-project-for-using-the-new/qaq-p/922677
-
I do, the sub-tasks would belong to the parent, but yes, there would be several of them, one for each number. Also, you wouldn't see them in the request portals, as sub-tasks aren't create-able or visible there. I'm not sure there's any way other than many "telephone number" fields.
-
Not reliably, there was one add-on that allowed it, sort of, but it's always caused problems when the data sets get large. It's really not that useful either - text is not something you should be building pi-charts against, as each text could be different, so you'd just end up with a chart made up of lots of single-point…
-
There's no way to do this - once you add a custom field, there is one place in the database for the data for that issue. I'm afraid you'll need to put the numbers into a text field, or play tricks like having several sub-tasks.
-
The result is what the script returns. You have no return value at the end, so it's coming out with null. I think you need to return either the assignee or the current value of the field (so it doesn't replace it with null)