Comments
-
Ok, it looks like you started the service as root once, which will clobber files all over the installation. Stop Jira and Confluence if they are running and use "chown -R <user>" on both the systems installation and data directories (the users are probably something like jira and conf)
-
I think I need more coffee, that first sentence just did not go into my brain!
-
Hey, no problem! I've learned something new from that, thank you!
-
>I created a jql and saved it, and using in custom report, i get no result. This sentence is a "microsoft statement" in your question - technically accurate, but utterly useless. Tell us what the JQL returns in the search, what "custom report" you are running and how it is working with the JQL
-
The error message is accurate - whatever database you have pointed Jira at contains some data. You need to give it an empty database to work with.
-
You have misunderstood what scrum estimation is for and how it works. The mistake here is "partially complete rollover" - this is nonsense and does not exist in Scrum. When you bring an item into a sprint, you are committing to completing it in that sprint. At the end of the sprint, the item is either done or is not. If an…
-
Go to Admin -> Issue -> Status, find the status and edit it, changing the status category to "done"
-
Yes, that's what the docs tell you to do.
-
Are Confluence and Jira running after starting them? What do their logs say?
-
Think there's a miskey in the most important part of the answer - your filter must contain "order by ranK" (and no other order)
-
Yes, there's a button for inserting a table in the editor's menu bar
-
The other part of it is "ow do I redirect my custom domain name to confluence" - to which the answer is that you need to set up DNS to resolve the custom domain name to the base url
-
I would create a sub-task for each person.
-
It is, yes.
-
Good point, it might not. It depends if the "do not allow edit" flag is set on the status.
-
Note that it says "if different to the web url" under the field. Cloud systems don't relocate the urls
-
Could you explain what this has to do with Confluence?
-
That suggests you have a workflow with just one transition called "issue" out of the current status. Most of us enable the "view workflow" option for our users and that is well worth a look to see what the workflow should be allowing you - "view workflow" hopefully appears next to the issue status, and will pop up a box to…
-
Custom fields are independent of each other, so no. Without scripting, the easiest answer is to use bulk-edit. Search for SEVERITY = 1, bulk edit the results to add Severity = 1, then repeat for 2, 3, 4, etc. When you've copied all the data across, kill off the old field.
-
This is a number that uniquely identifies the collection of logs you might want to send to Atlassian. It tells you nothing about the error. You will need to read the application logs to see what the underlying error is.
-
No, it'll start with the dashboard the user selects.
-
Your "done" status appears to be in the yellow "in progress" status category. I'd move it into the green "done" status category, and that should fix the report.
-
Ok, that's sensible as well. I would remove the unwanted plugin and its cached data before starting the upgrade though.
-
Are you visiting the page in the new path? You should not mess with the context path for synchrony unless there's a good reason to do so.
-
Ok, that's fine, you have a project context for release notes. Release notes are generated by version in Jira, and versions belong to projects, so when you go to the "create release note", it knows what the project is because it's for a version. So you don't need "current project", as you already have it.
-
There's no need to "clean" anything before an upgrade. But for disk space, yes, you can clear some stuff out (and it's nice to get clean logs when upgrading too) Do NOT remove any directories though, only look at the contents of them. There's no point in emptying the caches, plugin or temporary directories either,…
-
I'm with you @Scott Theus - the doc kind of says it, but in a very unclear way. If I were a new admin, I'd struggle to extract that info.
-
I feel I might be misunderstanding something, but this sounds like you want to have an issue that's in two status at the same time. That's not going to work - you need issues to be clear about where they are in the workflow. But, trying to think of what you've written differently makes me think that you might be talking…
-
Ah, crossed-over comments. Yes, you have the right way to creating a standard project there. It should ask you what template to use on the next step (independent ones won't)
-
Well, the fact you can't give it an issue type scheme is a good check that it is independent.