Comments
-
Yes, but it is pointless, as they were attached for a good reason.
-
No. You need to upgrade them to gadgets, there are different parameters and settings to work through.
-
You might have to, yes, although I would have expected a 4.x - 5.x upgrade to update them ok. Going from 3.x to 4.x would have been a problem, as "portlets" are removed and replaced with "gadgets", so I'd actually understand it if you've gone 3.x -> 4.x, not actually used 4.x because it's just a stepping stone and then…
-
So what are the gadgets you are using?
-
I would try restarting Jira quickly, assuming you have re-indexed (although the upgrade should have done that for you as one of the last tasks. You can check by running a search) If that doesn't help, then you need to check what the gadgets were in 4.4 and find out if they are still valid in 5.1. If they are, then you…
-
There's not really enough log file here to tell us what's going wrong. It looks like there's an error in the indexing during import, but that could be fine, as the index should be rebuilt after upgrade. But you then get a Crowd error, which is definitely a problem, but we can't tell what it is.
-
That's why I asked - most people hadn't noticed that little experiment had been added. People often use CSV and Excel interchangably, as it's a "big list of exported issues in a grid"
-
Do you mean the excel export?
-
I'm afraid they either have to be anonymous (no licence) or logged in (taking up a licence). There are some tricks you can think about - firewalling off the intranet from external access is a popular one, or proxying, so that people log into your proxy, but not Confluence so they remain anonymous.
-
Not really. I'm not aware of any addons that do any form of integration, but I know a number of people have written some simple stuff (Jira has email, SOAP and REST interfaces - I've seen email and SOAP used ini the past, but would expect more recent stuff to move to REST because SOAP is deprecated). However, you need to…
-
That's quite a hard one, because the answer depends on your configuration. I'm afraid what you need to do is go over every workflow looking for where you've used any JSU functions and work out which ones are breaking and why. There's no easy way to "fix" this, it is all about your config
-
I think you are conflating workflows and screens together. They are separate entities. * The workflow is completely independent of screens and is driven by the current status of an issue. The workflow in use is determined by your project and issue type (via the "workflow scheme"). * Screens are how you interact with…
-
As this is Cloud, I suspect this is referring to the events of 2 months ago, when they were removed? See https://confluence.atlassian.com/jirakb/jira-timesheet-reports-and-gadgets-removal-from-jira-cloud-792504481.html
-
Hmm, that doesn't really tell us much does it? The "disabling" line immediately after update tells us that it's killing the plugin as it's trying to load it, but not why. One thought though - you say it's a modified plugin, do you still have the original installed? Could they be conflicting? If not, then my instinct is to…
-
The "disabled on startup" symptom is typical of a failure of a plugin to load during the startup of Jira. You certainly need to remove it from web-inf/lib, it should not be in there. Once you've done that, you should provoke the failure again, restart Jira and read the log as it starts up. It should tell you why it's…
-
You do not. Cloud does not expose its database, or allow you to use others.
-
You need code to change those settings, they're standardised. Your "resolved" problem is an interesting one though - can you check the resolution on the issues in that status? I think you'll find the resolution isn't set, so JIRA doesn't think they're done. Also, if you're using a board, check that they're in the "done"…
-
It's not impossible, just not particularly easy to do in Jira because you'll need to code something that lets Jira understand whether a connection is from inside or outside and disallow connections based on group membership (the group bit is the easy part from memory). On a cosmetic point - Jira won't actually know to…
-
I wouldn't even think of trying this in Jira - you'd need to add code to make the login/authentication stuff aware of the source of the request. If you've got a web-server in front of Jira, like Apache, that's the sort of thing it's suited for. If no webserver, that's fine, but I'd look at the firewall as Renjith says.
-
Yes, you can.
-
It's a very generic error that is presented to the user to say "something has gone wrong and I can't really tell you what". The obvious possibilities are either that you've managed to give the macro parameters that it really cannot handle, or that something more serious has gone wrong on the server side. So, quickly check…
-
Um, the built-in filter gadget does that. The plugin you're referring to kind of died when Jira incorporated the ability to choose columns into the the core code.
-
You need to give it the username and password for the mail account on the mail server.Your "routing server" is not important here, you need to connect to mail.
-
Start with https://confluence.atlassian.com/display/JIRA/Creating+Issues+and+Comments+from+Email
-
Customers do not need licences from Service Desk version 2 and above. Check the project's setup for who is set up as a customer. See https://confluence.atlassian.com/servicedeskcloud/setting-up-service-desk-users-732528877.html
-
It drops columns it is unable to export. Yes, it should be reported as a bug. They're doing a lot of stuff on the CSV recently, so it might be flagged as a duplicate.
-
Correct, it's locked to prevent you editing it because you shouldn't. Delete is a little different, I'm not sure of the logic of that, but I suspect it's because the lock is a quite binary thing, on or off, no half-way "can't edit, but can delete" options. The correlation between locked fields and csv is I'm afraid,…
-
I asked for the names in case you'd run into one that was not an unusual field type. SLA and Time-on fields are indeed locked by Service Desk.
-
It's the field type - the code takes ownership of fields it doesn't want you to mess with. If it appears to be randomly locking fields of the standard types, then you've got some odd code or an admin doing it. What types are all of the fields you have that are locked? (And name might be handy)
-
Code. I don't think JIRA Core locks any fields, I'm not sure about Service Desk from memory, but JIRA Software locks a swathe of them. I suspect the ones you had before were Software related fields and when you upgraded, it went "I need to lock those" and did it. It's mainly done by field type, e.g. a rank field, or an…