Comments
-
There are massive problems trying to do this within various versions of 5.x. You really do need to go to the right version.
-
If you're trying to import a full xml backup of Confluence, you need to be importing it into a system of a similar compatible level. If it were a version 4 system for example, there's no chance of it working in 6. Or is it just space imports?
-
It's what it says on the tin. The Questions addon. See https://www.atlassian.com/software/confluence-questions
-
Yes. The licence is all about letting the right number of users in, it doesn't look at the data much.
-
The two systems you have are separate distinct installations of JIRA. They don't share anything. If one of you were on a Server installation of JIRA, then there are some options around mirroring a project (it would be duplicated in both systems and updated by both), but I'm not aware of any Connect add-ons or a method to…
-
The standard dashboard page can't really be changed much (without coding or addons) But you can simply point to any page in Confluence and say "that's the home page". And you can do what you want with a Confluence page. Just make sure it's in a space all your users can see.
-
Cloud can be billed monthly or annually. Server versions are an annual payment (it's a bit more complex than a simple annual payment though) See https://www.atlassian.com/licensing/cloud/managing
-
It does have a "transition linked issue" function. I don't know if it will do what you want, but it is definitely worth testing to see if it's right for you.
-
You will need to find or write code to do that (I'd do it in the script-runner add-on) The most simple solution is a post-function added to the transition(s) that should trigger the change on a linked issue. It will need to read over all the links, check the current status of the issues at the other end of the link, and…
-
Sounds like you've got something that automatically moves the issue. Start with a quick look at the issue history - look at the first two changes on the issue, what exactly do they say? Change of project or not? Then have a look at the listeners and post-functions you've got in the workflow.
-
Quite probably never. The current implementation is a "type 2" add-on which can only go into Cloud if Atlassian decide to support it. They're currently not accepting any new add-ons of that type. I don't know if a Connect version may in the works though
-
Hmm. It takes a long time and breaks because it's kind of the wrong approach - Jira simply isn't designed for massive data dumps, and doing it by extract (whether it's excel, xml, rest filters etc), you're going to run into performance issues, and it's very questionable practice demanding vast amounts of data for…
-
Well, REST will let you code more dynamic stuff, but it is still going to rely on you saying "run a filter for project X and then do stuff with the results" I think it might be worth asking what you're doing with this large extract - what's it for, why is it so large and why can't you do the work in Jira?
-
Definte a filter for "all issues in my project" and run it, so you get the list in the issue navigator. Then, look to the top right for views, and look on the list for "xml". Right click and copy the url. Anything hitting that url (curl, wget) will be handed the results as xml. It's more elegant to do it in REST of course…
-
Wiki markup is a convenience, a hangover from Confluence 3.x - it used to be the storage format, but it's moved to dynamic html, and the markup is just for formatting and us older people who still type in it. For a transform, I think you've got a couple of routes. First, export it to Word, as Confluence can import that…
-
In the Bitbucket database.
-
As an admin, click "create" under the project menu, and select a Service Desk type project, same as you do on Cloud.
-
Ah, yes, that's not the way I was using it, but I get that too in 5.9 now I've tested the specific case. I think you've found exactly the right bug, which is reporting it "found in 5.7 -> 5.8", and "fixed in 6.x". I think you've proved it is still there in 5.9 as well. I suspect we're stuck until 6 is available to us.
-
You've not explained what the actual problem is, so we can't tell you what may or may not have been "solved". (Bearing in mind that the macro seems fine in my 5.9, hence I've no way to guess what you might be seeing) Is there a bug for it logged at jira.atlassian.com? A public support request? Or just an older question…
-
You cannot edit the default workflow in Jira. Create a copy of the default workflow, put it into a new workflow scheme, and associate your project(s) with the new workflow scheme. You'll then have the option to edit the workflow (bear in mind that editing of active workflows is limited)
-
There is no "project type", those are templates, only used when initially creating a project. Select the right one there, and yes, but if you change a template (requires some code), it won't affect existing projects.
-
I'm afraid not. Category is just for grouping projects together for your users, it has nothing to say about the configuration of the projects.
-
It sounds like people are entering or changing the resolution as they go through the Resolved -> Closed transition in your workflow. Possibly by post-function? The resolution date really is just "the last time resolution changed from to <not null>" I'm not sure a "closed" date is of much use - I've got workflows that don't…
-
No. A JIRA admin is a JIRA admin. The whole of JIRA is built on sharing globally available objects, so the ability to administrate those must be global as well.
-
It has not changed, but I don't know why you think you need scripting or anything.Either1) Have one workflow and for each transition, one screen. Use field configurations to hide fields for different issue types2) Have different workflows for each issue type using different screens
-
Not directly. You could make a screen that includes all the fields for all the issue types, then use field context or configurations to hide the ones you don't need on an issue-type basis. Or you can define two separate transition screens and two separate workflows that use them (because you can say workflow 1 for issue…
-
System information or manage-applications will tell you. However, you're on Cloud, so the easy answer is "the latest version". The exact number will change faster than you can really use it.
-
Doesn't matter if it hasn't changed, the permission for "schedule" is what controls who can change the due date. You need to know that before you can look into changing it. There's several ways you might be controlling this, but we have to look at the permission scheme to start to unpick what you're doing (even if it's in…
-
Look in the permission scheme for the project. You'll find a line that says who can "schedule" issues.
-
Yes, and he made it abundently clear that this was an aspiration and that "when it's ready" is still the correct answer. If you trawl the forums and answers, you'll see that when estimates are given, they're rough, and never given until at least an Alpha version is knocking around. 5 isn't alpha yet, so you won't get…