Comments
-
... or how it should behave. Read only or editable.
-
Find or write a post-function to do it. You *still* need to tell us what you want from this field - you haven't answered the question about where you want it to appear.
-
Sumit's answer gives you a script field on an issue. This is a solution you've been told several times already, but ignored. It does not happen in the workflow. If you want to calculate a field in the workflow, then you need a post function (again, something you've been told several times before). The question that you've…
-
As Harry says, active-active won't work. Your failover server should be ready to run Jira but not start it until you have shut down (or lost) the primary Jira service. Your licence for the main server entitles you to set up disaster/failover servers at no extra cost. If you go to your my.atlassian account and look to the…
-
I'd break this up into steps. You have an 8.4 database and a working installation of JIRA (what version?) Stop it all and upgrade the database - does that cause the JIRA to stop working? Now what upgrade are you trying to do on the JIRA installation?
-
There's a number of things to try, but I'd probably be repeating what Atlassian support have told you. What have you tried so far?
-
Have you seen the "export to" functions at the top of the issue navigator? (Search for some issues and look near the top right of the results for an export/view option menu)
-
What data? You haven't enabled any tracking, so there's nothing tracked.
-
Have you enabled the Confluence statistics add-on (it's off by default as it can cause performance issues), or used a 3rd party add-on for the tracking?
-
Ahh, good. I'm a bit stuck on why it's asking you for a password from the CWD tables though - surely a restoration of a backup doesn't need an application password?
-
Actually, you are doing the right thing in recreating the database as it was shortly before the delete, but you need to do it in a separate database instance to begin with, then you need to extract the data from the temporary database. Personally, I wouldn't actually bother to try to run a Jira against the temporary…
-
I'm not exactly sure what you're trying to achieve here (get the issue SWTEST-8 back?) but it sounds like incremental recovery probably isn't the way to do it. (And I do hope you're doing it in a copy of the database, not the main one) It looks like the user you're trying to use didn't exist at the time that you've…
-
Of course you can add a custom field. But then it's not the due date.
-
That won't help, as due date is a date only.
-
Due dates don't have a time element, they're just a date. So I'm afraid there's nothing you can do.
-
It's a bigger number than your humans will be able to think through - there's no hard limit really, only what your server and admins can handle.
-
Checklists are not there to "replace subtasks" - a checklist is a list of things to tick off. A sub-task is a piece of work that helps you break down an issue so that it can be assigned to different people and/or represented as a discrete chunk of effort. There are cases where people use subtasks as though they are a…
-
Bother. When I saw this, it was because the wrong JVM was in use. But yours is fine. I think this one needs to go to Atlassian support - I can't replicate it, and I can't find any reason why it's failing. I'd give https://support.atlassian.com as much information as you can!
-
Ah, I think I've seen this before. Could you go to the JIRA "System information" page under the admin section and look at the Java related stuff - specifically, what Java is running and what version it is?
-
Could you look at the atlassian-jira.log file and see what errors are logged in there at the time a jpg upload fails?
-
Physically, yes. As long as their installations and data are completely separate, and the machine can take the load, it works fine (says he who once ran five on one box) You will need separate licences for each installation (Assuming they are all "production" - if you've got production, dev and test, you need one full…
-
First hit on any search: https://confluence.atlassian.com/jirakb/migrating-from-jira-server-to-jira-cloud-779160826.html
-
Yes, it's less than ideal in plain JIRA. Atlassian have a long-standing "let us edit fields in the issue navigator" request somewhere, but it always seems to be a lower priority than other stuff. JIRA Software adds some functions that can help, but they're focussed on boards (Scrum and Kanban) and still don't quite do it…
-
Take the filter for "assigned to me and needs prioritising" and run it as usual, then use "bulk edit". You can select which ones to change with a check list and then hit all of them in one go It's not individual priorities, you'll have to do it once for each priority you need to set, but at least you can hit several issues…
-
A "move" would be moving to the same version. If it's a new version, it IS an upgrade. You don't need any middleware or anything else - I mentioned both standard ways of *upgrading* a Confluence from 4 to 5 already - you should use one of them. 1. You could export and import - that is "old school". The import routines will…
-
That makes no sense. A "move" IS an upgrade. Confluence 5 can't use version 4 data, it MUST be upgraded to be readable to 5. So, no. If you exported the version 4 data and import it into version 5, or point a version 5 install at version 4 data, it will upgrade. Not move. Upgrade.
-
The assignee for a JIRA issue has to be a JIRA user. JIRA Service Desk has a slightly different model, in that customers (who are mostly not JIRA users) can be the assignee, in a sort of "it's their problem because they raised it, and need to tell support that it has been fixed" way. But someone who needs to work on an…
-
Yup, that's exactly what backups are for. It's no risk at all. (Although you need to think about attachments too)
-
Not without code (which you can't do in OnDemand) The closest I can think of - add a field of type "user picker" and then change your notification scheme so that it sends mail to anyone in that field. Not quite what you're asking for, but it will have the same effect on mail, just not add them as a "watcher"
-
I suspect you need to talk to whomever registered it already. However, support will be able to help you more than we can (we're end users, like yourself). Try https://support.atlassian.com