Comments
-
The export will contain all of your data, you won't lose anything. I would test the import a couple of times before you actually flip over to your new system - you can get an export of your OnDemand any time you want, withut having to switch it off, so grab it today and try it.
-
Change the status categories to "done" - go to Admin -> Status and change them there. Be warned it's a global change, if you're using those status in many workflows, it will affect them all.
-
Well, there's that, but look below the column title - it's yellow, meaning it's an "in progress" column.
-
That screenshot is great, it answers it in one go. Your "Done" column is not the last column in the board and is showing as the yellow "in progress". So the stuff in there is not "done"
-
Ok, what is the board filter for the backlog?
-
I'm unclear on what the problem is here - you appear to be setting a resolution (meaning "this issue is done with") at the right point in the workflow. The bit where I'm stuck is "The problem arises when we have some tasks as Done, these issues are not marked as done they are somehow incomplete". What, here, is "some tasks…
-
Ah, be careful with this - just because you are a project admin, does NOT mean you have any other permissions. Similarly for system admin - I currently have one Jira where I am a system admin and cannot see a single issue because I am ONLY a system admin, and not a real user (when I need to see stuff I temporarily move…
-
Yes, you can.
-
Generally, no, not unless you have a "watchers" field added to the create screen (there's an add-on for that) I don't understand "when I added the user to single user" - you don't add users to other users, it doesn't make sense.
-
There's loads of stuff this could be. You've covered field configuration and the fields being on screens, so the other things to check are: * Context - do the fields belong to the project and issue type you are looking at? (See list of custom fields in admin) * User selection - at the top right of some screens, you have…
-
Yes, that's a supported JVM, unlike the OpenJDK you were using.
-
No, it's not. There's a difference between OpenJDK and Oracle Java. You've fixed this by swapping to a supported JVM
-
Use a supported JVM. See https://confluence.atlassian.com/display/stash/Supported+Platforms
-
I can't think of a good reason to work that way either.
-
No, you're not missing anything. You've hit on the right idea, and, much as I usually avoid being so blunt, your previous admin was wrong. The assignee field in JIRA is designed to be "the person who is currently dealing with this issue". If they delegate parts of it out, fine, use sub-tasks or associated issues. If it's a…
-
You don't deploy a WAR for Apache, you create a WAR for Tomcat. Apache is usually used as a front end to do things like clever urls, relocation, ssl and so on, but you don't need it for simple one-offs like you are talking about. To run Jira with SSL (and no need for Apache), see…
-
The error message is telling you the problem - you haven't got the field on the issue edit screen.
-
That would require some coding - you'll need to add something into the core of the "issue view" that says "if project = X, do not render issue history". You could do an insecure version with javascript to hide the tab, but the raw html of the page will still have it, and Javascript is easy to work around/break. I think it…
-
No. Users go to the dashboard when they log in. That's the most logical place for them to land - on a page that they can customise to tell them things they need to know for themselves.
-
Oh, I'm sorry, I should have mentioned that when I was talking about coding. You have a limited set of admin rights for OnDemand, and I don't think you can disable the plugins that are considered "core". Such as the dashboards. I don't really think it's useful to turn off dashboards though - they're by far the best way to…
-
By disabling the plugins/modules that provide dashboards. Turn off every gadget except the login one. Obviously, if you disable dashboards people cannot use them at all.
-
Not without turning off the dashboards completely. They can always maintain their own dashboard.
-
You can't force dashboards on to individuals (without scripting/coding, which you can't do in OnDemand. And having them complain at you about messing with their settings, in my experience) You'll need to ask all of them to click "favourite" for themselves
-
A directory where you want to keep your Jira data. Best to start with an empty directory, as it'll create sub-directories as required. Never never never point it at a directory within the Jira/Tomcat installation. Frankly, it should be on a separate disk from the application installations.
-
You'll need to explain what you're trying to do with this. What do you mean by "contacts" here?
-
Then you aren't logging in as an administrator. My guess is that you created a second account, adn then either gave that one admin rights and deleted your own, or you are using the second account. Either way, you need to work out what you did and log in as an administrator.
-
When you installed it, it asked you to set up the first account. That account is an administrator. Do you have the admin cog at the top right or not?
-
Ask the person who installed it. As I said, they will have had to set up an initial user as the administrator.
-
Again, if you are not an adminstrator, then you need to get someone who is to add you as an admin. (By the way, when I said "click adminstrate", I meant click the "administrate cog", it's not a menu word there)
-
As you installed it, the first user would have been set up as an administrator If you are that user, then click "administrate" at the top right. If you are not, then you need to get them to add you to the admin group. Normal users cannot create projects.