Comments
-
When you use a browser to connect to a service such as Confluence, you connect to an address with at least one "port". Localhost means "this machine" and 8090 is the port. The ports enable the same machine to run several channels for many services on the same address and a lot of them have recommended defaults to expect…
-
This has nothing to do with the database - the fact you get that login page means that Jira is up and running and connected to the database. You should not be logging in there with the database connections, you should be logging in with a Jira account.
-
You will need to find or write a listener that can detect "issue changed", check if things were attached to it, then copy them over to the ftp service
-
It means Confluence is not running on that port on your machine. You'll need to check if it is running, and if it is, where it is actually listening.
-
See https://confluence.atlassian.com/adminjiraserver/importing-data-from-csv-938847533.html
-
Ok, I can't see anything wrong with this. Could you try re-indexing the project?
-
You will need to convert or export the mpp file to CSV, then you can add a column to indicate the parent issue(s) for each sub-task you import.
-
You will need to create customer accounts from these email addresses, then you'll be able to add them to the request participants field.
-
There's a "close comment" tag on the first line of your server.xml in your question, but I suspect you're also missing the flags from the connector. You've actually commented them out - look for secure, scheme and proxyName
-
Ok, plain Jira. How are you wanting to represent the test plans in Jira?
-
What test planning app are you importing into? Or is it just plain Jira?
-
Yes, all of that is right.
-
What "integration"?
-
You should not yank the platform out from under Jira, you will break it. You should upgrade Jira to a version that is based on Tomcat 8.
-
What test planning app are you importing into? Or is it just plain Jira?
-
issue.getStatus() should give you the status of the issue so you can test against it.
-
Yes, almost everyone I've worked with customises the list of resolutions. As long as you don't make the mistake of using resolution for things other than "this is why we are not going to do any (more) work on this", you should use a list that tells you usefully why something is closed when you're reporting. Usually…
-
For coding, I tend to start at the tutorial point - https://developer.atlassian.com/server/jira/platform/creating-a-jira-report/
-
You can create your own reports by writing code and adding apps to Jira. My guess on the boards is that you do not have the "create shared object" global permission. (Note that admin permission means you have admin rights, not "can do anything" as that's a terrible security model)
-
Yes. Dashboards and boards use REST to get some of their data. If the REST api is unavailable, large swathes of Jira will not work. You need to stop blocking REST, it is going to break it for you. Yes, you can access it anonymously, in full. What it returns is limited to what anonymous users can see in the UI.
-
I suspect you have "rich text" enabled for your comments, which means Jira tries to interpret markup, rather than plain text. In markup, two underscores in a row is a formatting instruction, not text, so when you use them in the text, they are being dropped because they are seen as instructions, not data. I think the…
-
What do you mean by "assessment"? Is it a field?
-
You will need to look at apps that provide workflow post-functions that can select and set the assignees you want according to your needs.
-
Looking after a Jira system is the way most of us learn to become Jira admins. I would also seek out training and maybe look at getting certification (as the learning for that is a good basis for being an admin)
-
Have a look at the link Earl gave us, it covers that.
-
Could you explain what this has to do with Confluence?
-
All we can tell you here is that your dbconfig.xml is wrong, or the database that you have restored is not right. Could you tell us, in more detail, what you have done and what the errors/messages are as Jira starts up?
-
Could you read the log for the problems around these lines? Grep'ping for error has suppressed the warnings thrown that lead to the errors, so we can't see what has been failing.
-
You would need to split it into two transitions, or write some quite complex code.
-
JQL returns lists of issues, not versions. The only way to do what you want is to use JQL to find issues and then report on them in a gadget on a dashboard.