Comments
-
In Jira, when you click "create project".
-
Go to "manage applications" in the admin section and enable or install it.
-
It's at the bottom of the template selection window.
-
No. The original estimate belongs to any issue type you choose it to belong to. By default, it's the issue types at the "issue" level (because Jira Software is built for Scrum, which means estimates on sub-tasks are mostly useless). So when you look at the issues in a sprint, you'll get all the estimates for the…
-
My guess is that the "closed" status was not in the right-hand column of the board, and the fix was to put it in the last column.
-
See https://confluence.atlassian.com/servicedesk/jira-service-desk-3-10-x-upgrade-notes-941610929.html
-
To modify the menus that are built into Jira, you will need to open up, edit and recompile the plugins that are part of the core (this will invalidate your support as well as make it a monumental pain to upgrade Jira).
-
What "flow chart"? Please, you need to tell us what you are asking about, not just make disassociated statements that have nothing to do with Jura.
-
Boards have been completely rebuilt since this conversation ended 5 years ago. If you want to see closed issues on your board now, you can. Just configure it so that it does not hide them.,
-
The "issue detail" screen is usually the "view" screen, but I'm guessing you are talking about one of the board view screens, which are less customisable. They'll respect the fields you remove from "view", but have a fixed order that you can't do much with. You can try Board -> Board Configuration -> Issue, but might not…
-
Probably time to contact support then, with a description of the error.
-
You don't. Projects do not have a status for you to update. I think you are asking about something else, but I can't guess what from your question. Could you give us more detail?
-
Each menu item has a "weight" property in its plugin definition. The menu is ordered by weight, low at the top, higher at the bottom.
-
The only way to do what you want to here is to find or write code to do it.
-
Go to the project admin section and find the "issue type screen scheme", go into that and you'll find it tells the project which "screen scheme" to use for each issue type. Go into the one you want to change, and you'll see it tells you what "screen" to use for view, edit and create. You can add, remove and reposition all…
-
Confluence doesn't have "folders", but you could create a set of pages in a tree to make it look similar. It's also not designed as an object management system, it's a wiki. Most of the contents of what you've got in document files would be expected to become sets of pages. So it doesn't really have any structure to accept…
-
What do you mean by "integrate"? The word tells us you want the two to work together, but because it tells us nothing more, it's useless as a question. What do you want them to do together? There are some add-ons for both products that do specific things, but you'll need to look at them for yourself to see if they do what…
-
We can't tell you a lot more than "use Confluence as it is intended". It's got a system of storage and maintenance for managing information in spaces and pages, and access control for your users, whether "outsider" or not.
-
CentOS or Ubuntu is entirely up to you - it works fine on both. You should pick the one you are happier to look after. For sizing, see https://confluence.atlassian.com/doc/server-hardware-requirements-guide-30736403.html For docs, start at https://confluence.atlassian.com/doc/confluence-server-documentation-135922.html
-
A project is a container for issues, and is pointless without them. For Jira, it's complete nonsense to hide the project that contains issues the user can see. So there's no way to do this. If you want to allow someone to see an issue, they have to be able to see the container project.
-
Follow the prompts through. You are changing the workflow and you have changed the possible status, removing at least one status. When you do this, Jira can't leave existing issues with status you have removed, it needs to give them a status in the new workflow so that they can be used. So you need to tell it what new…
-
Sounds like it. There's a good reason the docs all say you should not use h2 for anything other than dev and test.
-
I don't quite get what you think I have misunderstood. I understand relevance of attachments to issues and that has nothing to do with the underlying storage. I think you've read more into what I've said and not quite got what I was getting at (six years ago, but it's still right) On the technical side - store the files…
-
There is a "delete page" option in the page tools menu. But only if your space admin has given you the permission to delete pages in the space.
-
SQL is the worst possible way to report on jira data. But if you insist, then it is important to understand that most Jira tables have an id that uniquely identifies a record in them (you don't need that in a proper database, but that's one of many reasons reporting this way is bad. The Jira database is NOT a database,…
-
Run a search for issues, bulk-edit then appears as an option on the tools menu (... towards the top right) for the search result
-
The project url is just a field for a url that the project can use to point to something else. Most of us use it to point to a Confluence space for the project docs.
-
What do you mean by "metadata" and where? You have not given us any context for your question, so we can't work out what to tell you.
-
I'd strongly recommend using add-ons. You can disable them easily if you have problems and need support (any hacks to the core or injected js render your Jira unsupported), and most are written by experts in Atlassian software.
-
Ah, I had assumed you were importing issues. You will need to shut-down Jira to allow Crowd to pull data directly from Jira's database into its own.