Comments
-
That suggests that the workflows are not using those screens in transitions. Could you check which screens the workflows are using for transitions?
-
Whatever reporting tool you want to use, it will have to read JIRA's data over REST. You won't get access to the database or other ways to access your data.
-
Yes, but you'll need to define what you want from this "integration" before we can tell you much more about it. On the licences, yes, you will need to pay for both servers.
-
Yes, the links are trying to tell the users what has changed and take them directly to the change. In the case of attachments for example, if I get an email saying "issue updated", I kind of want to know what the update was, and you can't actually tell without consulting the history. If you don't like this behaviour (most…
-
I suspect it's because the world is moving to 64 bit. The (relatively) simple process for you would indeed be to unzip the archive to a new location, check it works empty, without looking at your existing data, and then copy the home directory from the old install to the new one. This should cause it to read your data and…
-
You don't. Atlassian dropped support for 32 bit installers from 6.0 onwards. There's a mention of it in the early access notes, and at https://confluence.atlassian.com/doc/confluence-6-0-upgrade-notes-844235311.html#Confluence6.0UpgradeNotes-32-bitinstallersnotavailable You'll need a manual install from tar.gz See…
-
Also, if you read further down the log, you *might* find a "caused by" entry with the class of the missing add-on named.
-
I'm not sure about the fix version idea there - they're there to say where you planned to fix it, and when you did, it's not for flagged something as closed.
-
Paulo's suggestion does open up your issues to all edits - the other option is to have a transition from closed to closed, with a screen on it that allows the user to update whatever fields you want to allow them to change. It might also be worth a look at your process - should you really be reviewing closed stuff for…
-
Sounds like you have used the standard export and not a Jira workflow bundle - that's what my answer was about.
-
Fields and screens are NOT part of the workflow. They are configured in Jira and then referred to (if needed) by the workflow. I'm not sure where you got the impression that they are in the workflow from. You will need to create supporting screens and fields in the target Jira if you want to move a workflow from one system…
-
Yes, if no-one has written to it since Friday (With any data you want to keep), then restoring the Friday database dump and reindexing should fix it. You will need Confluence offline while that is done though!
-
Well, the copy is a good start, but that isn't the main worry. The problem is that you need to replay over 30 days of data into the new database. My (very limited) understanding of a MySQL dump is that it is possible to convert it into the statements you need from it relatively easily, but you've got two problems with that…
-
That could be quite difficult I'm afraid. I assume you are talking mostly about the edits to Confluence pages that you have lost because you've effectively rolled the system back to June 2013. These will still be in the database on the old disk, but that assumes the database was physically on that disk, and it wasn't…
-
Have you tried clicking "Create" and then "Blog"?
-
What have you done differently from the documentation for it?
-
Ah, wiki markup only works in the editor now. You should find html works though, although I suspect that may go eventually.
-
What 'rich text' have you added?
-
I don't understand what you're trying to do here, export something or fix something? You lose me after "can export to XML".
-
If you want to stop them seeing other projects, you are going to have to re-build the access to those projects. JIRA ships with a default permission scheme that sets every project up with "if you can log in, you are allowed to use the project" - you'll need to pull that out of every project you have. I would strongly…
-
That's the way it works. You must be getting the update for another reason - a second user with your email address (the setting filters by user id, not duplicate mail addresses), membership of an email group (not a jira group - it's clever enough to get those too, and roles!) or something on your mail server.
-
Go to your profile and unselect "email me on my changes" in the preferences. You might want to consider doing that with the default user account as well, if you're an admin.
-
If the new issue types are not offered to you on "create" then you have not added them to the "issue type scheme" for the project. You can find that under project admin See https://confluence.atlassian.com/display/JIRA/Associating+Issue+Types+with+Projects
-
Not all mail clients have the ability to set a priority, but when they do, it should work as Raffaele describes.
-
Check the notification scheme first, and that the users who shouldbe getting the emails have permissions to see the issues.
-
Your idea about simply disconnecting the old 32 bit and pointing a 64 bit installation at the same database is the way I'd do it. I assume attachments are held under jira.home. If you're moving machines, you will need to fiddle with the licenses, but that's about the only real gotcha I know of. I would take a backup of the…
-
You have read it correctly (for all versions of Jira - 2.something to the current version). You have to be a Jira system admin, or a Jira admin, in order to create a project. To allow lesser mortals project-create needs plugins/code/etc
-
That's one of the things Confluence does (better than trying to kludge something into an issue tracker that is not for documentation or attachment management). You might want to add that to your OnDemand account.
-
Nope, that's wrong, Behaviours became part of it over a year ago. Unless you're on a quite old version, Behaviours is in the Script Runner.
-
You'd need to write a new custom field type to be able to do that. The logical structure of the internal cascading select is parent/child, not free-form. You might be able to do it with two standard select lists though, linked by Behaviours from the Script Runner add-on