Comments
-
Essentially, you can't - javascript hacks in JIRA are gradually being disabled, and the approach here is to get a good answer to "why are you trying to put useless data into fields?". What are you trying to achieve by pre-populating the description? Why haven't you split that up into custom fields which do take defaults?…
-
JIRA Software is an application that sits on top of JIRA Core (Think of "Core" as being the platform for other applications such as Software). All you have to do is re-add Software back in from Admin -> Manage Applications.
-
It looks like the mail server you are connected to is not correctly configured. Could you check ALL the configuration of the incoming mail service?
-
Then, as above, you don't have system rights and won't get them. Your lower-level adminstrator accounts are maintainable as they always have been (updates would not have changed that) As stated already, go to "global permissions" to see what groups have Admin rights and then use the group maintenance to view/add/remove the…
-
To recover admin rights, please follow the instructions given on the page John referred you to. We can't tell you which approach is most appropriate because we don't really know what has gone wrong - you need to tell us what you have done (John took a guess that you're restoring an OnDemand backup - that's one thing it…
-
Yes, that's why we have test systems. We can do all the testing in there and clean it up by rebuilding. "Do it in live" is something the industry has been trying to stamp out for years.
-
It's not a system that expects you to set up and destroy loads of projects like that, it's expecting you to create the projects you need and work with them. It's not so much that JIRA is inefficient, more that what you're doing is. JIRA Server is no different, but it does have the advantage that you can add scripting or…
-
Manually, on Cloud, and you'll find there may be traces you can't remove. Once you've deleted the projects, you'll need to go to each scheme section in admin and click delete for each inactive item you don't want.
-
Paid, but well worth it if you want to do anything clever with email
-
You need to use a mail handler that understands your fields. The default mail handlers are not that clever - you need to find or write a handler that can cope with your mandatory fields. I always reach for JEMH as soon as I want to do anything with incoming emails.
-
Sorry, I should have said Go ahead and set up your project. Your dashboards might need to be reconfigured to look at the issues in it. Your board(s) can be created at the same time as the project, or later (the "create board from existing project" option is quite neat, and you can still go back and change the filter for it…
-
No Again, the board and the dashboard are views. There's no "move" of anything. You just set up the board to look at something that's in a place. The issues do not change when you create or configure a board.
-
Dashboards and Scrum boards are not issue containers, they are a view of things (mostly issues that live in project containers) To get an issue to appear on a board, the board's filter simply needs to include the issue. So look at the filter - mostly they are simple ones like "project = xyz", but they can be complex. You…
-
They can't. Script Runner is not (yet) available for Cloud.
-
It's not a case of "fixes", you're talking about having to restructure a database and its content manually.
-
Ah, ok. If they doubt the answer, then tell them that they will need to read all the upgrade code in each version and perform each task manually. I'm pretty sure that they will quickly see that stepped upgrades is a lot safer and quicker.
-
Technically, mathematically, yes, although it's going to take you decades to do the fixes. A slightly better approach might be to take the database and run it through all the changes needed by running the SQL, but that's not going to be a lot quicker. You could probably get it down to a few years by reading every line of…
-
You'll need to give us more of the logs to help you with that.
-
Hmm. I'd say it's a bug in the JMWE then - putting in the string "Batman" should set the Summary to Batman. That's what the help and the documentation says - "return a string that will be converted", and "Batman" is exactly that.My only other thought is that maybe the JMWE expects an explicit "return", which feels wrong to…
-
Hang on, that's different again.I'd go back to basics - does a plain fixed string work? E.g. just put in "Batman" or something obvious.Also, where did you get the " issue.get " type notation from?
-
It looks like issue.get("customfield_12230") is returning an array, rather than a string. Is the field a multi-select or checkbox field? Another quick dirty test would be to try issue.get("customfield_12230").toString() and see what that returns - if it's an array, you'll get an ugly string like "[ armadillo ] @ […
-
There is no safe or supported way to downgrade a JIRA, the strongest recommendation will be to avoid doing this until you have upgraded the target JIRA to 6.3.12. (You could try fiddling with the build numbers in the database to trick the 6.3.12 version into thinking the data is from 6.3.12, but that is unreliable and…
-
I vaguely remember something like that in an old version of Greenhopper, but I'm really not sure it was estimates. That's definitely not the way Agile now works though.
-
That's controlled by whether you put the estimate fields on the issue types in the projects (using field context and/or field configuration)
-
It's not project setting, it's done by the board. So, go to the board, configure, estimation tab...
-
It's not that simple - it really does sound like you were using LDAP before, and even if you weren't, you could have been using something else. If you really were using internal authentication on the old system, then the table you need is cwd_user But you won't find passwords there - they are NOT stored (it's really bad to…
-
You should be using one of the users from your original installation - these will have been imported as part of your data. If you haven't got any, then you were using LDAP...
-
Well, um, yes. Don't put the LDAP stuff into the config file. If you aren't using it, then you shouldn't have enabled it in the first place.
-
I'm confused as well - you really should have known whether your system is using LDAP or not. We can't tell you from that because we don't know your configuration. So, a bit of guess work here. If it seems to have been used that way in your old configuration, then the short answer is that whoever told you that you don't…
-
The settings should not really have changed, assuming your LDAP server has not changed. Your log is telling you that it can't actually connect, so your settings are probably actually fine, and the issue is with your network - the Jira server cannot reach the LDAP one (connection timeout, rather than "connected ok, but…