Comments
-
Not in Jira. Jira needs a single database connection, it won't write to two databases. So forget that idea straight away. However, you are on the right track. Most database servers allow you to replicate. The server listens for changes in database A and copies the changes over to database B. The Jira connected to database…
-
Have you got the timetracking field on the issue "create" screen?
-
For JIRA, start with a read through https://confluence.atlassian.com/jira/migrating-from-other-issue-trackers-119334.html
-
The main visible changes are related to users and their access, you may want to revise your groups. The other effects are dependent on how you're using it, but the migration hub does mention most of them. The one I'm not sure it emphasises enough is add-ons. Some stop working and need to be removed or alternatives found,…
-
Yes, you should upgrade to the latest version. The licencing depends on the dates. If your licences are current, then you can upgrade to the latest version with them. If they have expired, then you might not be able to upgrade to a version high enough to be compatible. However, Atlassian will not punish you for using…
-
Ah, that's an easy one then. Create a new project category for each "client" and stick each project in the right one. You can then use the search "category = x" to pull all issues for a client across all their projects. (Or even "category in (x, y, z)")
-
It depends on what you want from the relationship. What would "setting a client" be aimed at getting you? I've got some suggestions, but the best option very much depends on what you expect the association to actually do!
-
You don't, the structure of a Cloud installation of JIRA, Confluence etc is fixed. If you want to run the applications completely separately, then you can buy another Cloud installation
-
It happens automatically. A board selects a set of issues. If you create a new issue, it needs to match the criteria for that board. I suspect your board says something like "project = X" and you've created the issue in project Y, so it's not in the backlog. Or "project = X and status != new" and the new issue is in status…
-
I'm not sure I can be any longer. Yes, you can use a $10 licence on a server. That's what it's for.
-
See https://confluence.atlassian.com/display/DOC/Confluence+Installation+Guide You'll need to ftp the installation files up to the server and log in to set it up, but you can do it as a non-root user. It's less than ideal - I'd usually recommend running it as a user dedicated to the application, and you won't be able to…
-
I would say you are lacking the global permission to create shared objects. Check admin -> global permissions
-
Actually, the version still doesn't matter - Cloud is always the very latest version. So when you get to step 2 in https://confluence.atlassian.com/confcloud/migrate-from-confluence-cloud-to-server-724765578.html you need to grab the latest version from there too.
-
Ah, I hadn't looked recently. I thought standard admins (above space admins, but below system admin) could see the system information page in Confluence Cloud. I'm not sure the version actually matters that much - it's Cloud, you don't get any choice about the version (it's always "latest") and the Cloud docs should match…
-
It's the latest version of Confluence that Atlassian have released to Cloud, always. You can see the exact version at the bottom of the page. If you have no permissions for that page, then you are not an admin for the installation. You'll need to talk to your admins to get access.
-
Fields cannot be restricted like that. You'll need to get the users into different projects, which can have different sets of options for fields.
-
That's correct, a date field can only show one date. If you want to track more than one, you need to think about how to trap it and report on it. The trick I've used in the past is to have a text field as well as the date, and a post-function that appends the date to the text when the transition is used.
-
I'd suggest you grap a copy of the code from your myatlassian account. If you have a commercial licence for Jira, you can download that for any version you need. If you don't have a licence, then I'm afraid we can't share the code, as it's privileged.
-
You would need to hack the core code to do this, which is not something I'd recommend. It sounds like you need to use a different page for your plugin, although you could copy the one from the code in the core of Jira of course, as a starting point. Note also that jspa pages do not exist, they're generated on the fly by…
-
Yes
-
No, the Roadmap is built with the assumption that you will be using fix version and nothing else. You could grab the source (if you have a commercial licence) and modify the plugin that provides the roadmap function of course, but I don't know if it's using a simple query (if it is, then adding "or in custom field X"…
-
No, it's a bit of a pain to add anything to the standalone installations. It's much cleaner to start with an empty Tomcat and configure the WARs independently. You should be able to follow the instructions for each pretty much independently!
-
Are you trying to run Jira and Confluence inside the same Tomcat as Jira? Three points on doing that * It's not recommended or supported * You need to do quite a bit more than just tweak server.xml to get it to work if you really do want to run them inside the same container. * Jira standalone is built to run Jira, if you…
-
REST doesn't do anything differently to the UI in the back-end, so it's not that. You need to be looking at addons, broken workflows or system crashes.
-
The usual culprit is that the workflow table does not match the issue table. Try running the integrity checker from the admin section first - that specifically fixes issues in this state. Also, you probably want to try to work out why this has broken. The main culprits are people trying to be "clever" in transitions and…
-
Yes, you've run out of agents. Either remove ones you don't need any more to make space for new ones, or upgrade the licence.
-
Yes. First, you need to grant everyone access to see the space, as a space creator. Then, assuming they have the "restrict" permission, your users can create pages which are read-only or even hidden, and their child pages will take on the same visibility. It's quite common to see spaces which have the simple approach -…
-
Ok, always worth a try. Could you look in the database and see if there are actually any issues in it? As you're using HSQL (which can fail catastrophically, which is what I'm starting to worry about here), you can simply open the file in a text editor (when Jira is offline, and be careful to keep it read-only) and look…
-
Hmm. Could you try a full re-index? If you've simply restored the data, then your empty Jira won't have had a chance to build the index...
-
Ok. Hsql then. You have not told us what you did to "migrate". Was it a full export and import into an empty system? Or did you simply try to move the whole database?The instructions you read probably mentioned export and import, so what did you do there?