Comments
-
https://confluence.atlassian.com/adminjiraserver071/migrating-jira-applications-to-another-server-802592269.html is where I start, but adjust it for your version of Jira
-
1) There's an option between "off the shelf" and "write my own" - look in the marketplace for something. There are several "advanced table" apps in the marketplace for Confluence. You can usually get to it from within Confluence - go to admin -> manage add-ons -> find new. Confluence is a wiki, aimed at free-format…
-
Not without writing your own add-on to provide it. The message fields are a simple implementation to inject text, which are more of a work-around than a proper fix. A proper way to do it would be to have panels you can inject, but there's no framework for arranging them, unlike with fields where you can move them around.
-
Doing it by hand, copying from one window to another.
-
Confluence is a wiki, aimed at free-form documentation, not forms. But, to help you with that, it has templates. You could write a "project description" template and make that globally available.
-
The problem you have with burndown is that it has to be time-boxed, which simply isn't there in Kanban. However, you say "I am no longer able to create a sprint board" - why is that? You should be able to create a new board, adjust its filter to include many projects and work off that.
-
No. Moving to another server does not require the purchase of new licences (unless you want support). You will need to buy if you upgrade to a version released after the end of your current licence.
-
You can't. CSV is not powerful enough to support the data structures the configuration of the data would require without writing a vast amount of code to provide a kludged data structure export and import. In fact, Jira can only do it in one format, xml, and that is limited to doing everything, not one project as Atlassian…
-
Debugging and tuning JVMs is not a small or simple subject. You've only given us part of the JVM settings, and we'd need a lot more from the environment, we don't know the java version, if you're using a proxy, your logging levels (which usually need to be increased to help track down crashes), the exact symptoms (sudden…
-
Actually, sprint start date is not set quite automatically. It is entered by the user when they create or start the sprint, and then read from the sprint when needed. The only fields the system fills directly are creator, created date and updated date. Everything else is entered by users, or derived from combinations of…
-
Thanks, that has cleared it up perfectly. You say > so I created an "unresolved" resolution That is the problem. You should never do that. Now what you need to do is: * Rename "unresolved" to "do not use" or something equally off-putting * Look at where you have put it on screens. You must never have it on* Create * Edit *…
-
Again - fields are updated when the user changes them. I'm stuck on what you don't understand about that.
-
That's correct, you made 8 points "done", so it's knocked 8 off the sprint total.
-
You're doing nothing wrong, that's the way the field has been written to work.
-
I'm sorry, I do not understand that. (It's been a long day, I'm struggling) When you go to Admin -> Issues -> Resolutions, is there "unresolved" on the list anywhere?
-
Not sure what you mean by "PC users" or "credentials"? How are they defined in your Jira? If however, "PC users" just means "users", then try creator != currentUser() That will list all issues created by people other than the person running the filter.
-
It looks to me like one of your inexperienced adminstrators has added "unresolved" to the list of resolutions. Go to Admin -> Issues -> Resolutions and look at the list. If it has "unresolved" on it (or any other phrase that means "not closed"), edit it and change it to "Broken Resolution option - do NOT select this". Then…
-
I suspect the Account field has different contexts, so the value in one project may not be valid in another.
-
Correct, but do you have 60 permission schemes? Or are they sharing some?
-
I'd copy the module that makes the template to another name, adjust that, recompile it, add the new App, then go into manage add-ons and disable the module providing the system-provided template. That way, you won't render yourself totally unsupported and having to hack the core on every upgrade.
-
You should be able to upload your own icons for the priorities, in Admin -> Issues -> priorities
-
So they can see the issues in the "done" column? You need to decide whether verified issues are done (according to your definition of done for the board). If they are, then you need them in the done column to count towards burndown and velocity. If they are not done, then they can go in their own column that clearly shows…
-
Code. You would need to write a new version of the gadget that selects differently and looks at the issue history for your definitions. Forget "resolved status", it's irrelevant here, but use the resolution field as intended. Assuming you do not want your users to get involved with setting resolutions, amend your workflows…
-
I think I know "Odyssey" - it's a wrapper for Atlassian tools in a certain company. If you want other issue types, you'll need to talk to the Odyssey admins, but it's not likely to happen as they've configured it to be used in standardised ways. If you are stuck with this list, then I would usually see a "requirement"…
-
That suggests you are not looking in the home directory you told it to use. If the application is running ok, have a look at the "system information" page, that will tell you what it is using for home.
-
You have the right idea - Done and Verified both need to be in the last right-hand column ("done"). But your team members should be able to view that in the board. Are you saying everyone cannot see the issues, or is it just your team members? Or is it by status? (You can see verified issues, but not done)?
-
If you take a filter as Igor suggested, you can display it through a Jira Dashboard gadget, and draw that into Confluence. If you use a "statistics" gadget, you can group the results in the filter by a field. Selecting "assignee" will then give you a count of all the issues each person has. A difficulty might be how you…
-
The problem here is your permission schemes for "all projects" allows "any logged in user" and/or "people who are in the Software access group" see and use the projects. To "limit" someone to a small range of projects, you need to un-pick that - change the permission schemes so that they only allow people/groups in the…
-
They don't have the admin rights that enable them to delete projects. Also, you can't re-use project keys without some complex manipulation of the database that you can't do on Cloud. (At least, this was the case last time I deleted in Cloud, it may have moved on by now)
-
It's usually the first field on every line in the files called access_log