Comments
-
I don't know quite what this has to do with Confluence to be honest.
-
Ran into it on Friday myself. I know it sort of makes sense when you think it through, but it's not obvious or intuitive! And I keep forgetting it.
-
What type of custom field is "Request Type"? Also, could you check the field context and the field configurations - I suspect you might find 152 issues are in projects that the field does not exist for.
-
They have misled you. Kayako is not an Atlassian product.
-
Could you explain what this has to do with Atlassian products?
-
To what extent is it "stopping email notification"?
-
Google takes you to "how to install plugins" in Atlassian's documentation. Typing "install plugins" into the search in the documentation takes you to the right pages. The software itself has a "plugin manager" (Which you'd know if you'd read the docs) which tells you how to install stuff on-screen. I am sorry if I am being…
-
Then why are you quoting this random page off the internet? Where does it say in the confluence documentation, to use that page for installing plugins? What's it got to do with Confluence? Have you looked for "installing plugins" in the Confluence documentation?
-
What? Eh? Why are you picking random pages off the internet instead of reading the application documentation? Have you not even looked for "plugin" in the Confluence documentation?
-
You haven't really pointed us at which plugin you're talking about. I'd assume that the plugin documentation contains instructions, unless they're the most simple case: "install via universal plugin manager and it works.
-
That's what I'd use, but you can do it with your own add-ons too (before Script Runner, I wrote a couple of fields that extracted the history and put them into the navigator, and I had a timeline of changes report for issues as well), There could be other add-ons out there that might help too, but I'm rusty on them because…
-
For a single issue, look at the history. For many issues, you'll need to write code that can pull the data out of an issue history. I suggested fields initially because they would come out on the issue navigator and hence be exposed to excel downloads, and you'd be able to search/sort on them. If you're now wanting to…
-
Code - you'll need to find/write fields that can pull that data out of an issue history and then display it in the issue navigator.
-
Mmm. Is it possible to create a temporary installation (a local standalone version with the local hsql database with a dev licence or even a developer system using the SDK will do this) and try importing the whole thing into it? That will validate the xml, and prove if the versions are right too. You still need to get the…
-
Looks like the xml in your backup is invalid. It might be because of missing data though (do the issue types in your system match the issue types in the source system? You need to make the source have all the issue types you are importing)
-
Not really, there's not enough information. (An NPE in Java really is a catchall error - it could be almost anything) Please have another look at the log file and post the errors in there. At the very least, the handful of lines around the one you've posted.
-
Yes, as you say, with a condition.
-
Start at https://confluence.atlassian.com/display/JIRA/Configuring+Fields+and+Screensfor fields and screens. For the stuff about assignable/can-assign, look to the left of that page for the help with "permissions"
-
What do you mean by "configure" the field? * It offers the user a list of users determined by them having the "can be assigned issues" permission in the project * To determine where it appears, you edit the screens in Jira * The field will only be available to people who have the "can assign issues" permission in the…
-
As an admin, create a new project in your system. Give it a permission scheme that hides it from the other users, and test away. Or if you're asking about an entire JIRA system, either sign up for a Cloud account or download the Server version and use an evaluation licence
-
I think you're missing the point - if OnDemand is using the version called OD-6.3, and your production version is plain 6.2 (which means "download 6.2"), you can import the data. You don't need the same version as OnDemand, just a close-ish one.
-
Actually, no, you are wrong. It works within certain ranges. Try exporting from OD, and importing on the version od-1 or od-2. You get a huge great warning about losses of functionality, bit the import works. Lower I've tried it with is a target of 6.1 from od6.3, bit it is working
-
That is correct - project import has always required the data versions to be the same.
-
Later versions of downloaded Jira allow you to skip the build check. If you export from OnDemand now (which is on 6.2), and download 6.1, you'll get a warning, but it will import the backup file without you having to change anything.
-
If the filter owners are actually using the filters, you'll find they get an error, not a zero result... Udo beat me to the SQL
-
I'm not sure there's any reason to bother. If a filter is private, only the owner can see it, and when they use it, they'll see it's broken and know they have to fix it. Doesn't affect other people. If you do have some reason to do this, then you'll need to go via the database.
-
What do you mean by "messages" and "one enhancements"?
-
See https://marketplace.atlassian.com/search?hosting=cloud&product=jira&query=asset The results all have install instructions
-
By the way, that is a very specific piece of advice about the database. If you are touching any part of Jira that may be cached, counted or active, then you will break your Jira by amending the database while it's running. I don't believe the user's email addresses are cached, so this should be safe. BUT, almost everything…
-
Have you tried what John recommended, and then read the log to see if there are errors in it?