Comments
-
The screenshot on the right suggests that your nginx setup is incorrect. What have you done differently to the doc?
-
Yes. The servers don't care what type of licence the other server has.
-
All I can tell you is that there is something wrong in the script - it's not passing Jira a valid set of credentials. But I think your Captcha instinct is almost certainly spot-on - once you've failed login a few times, you'll need to pass that test to allow login.
-
Assuming BCP is something to do with "Business Continuity" and not the more commonly used acronyms: >What are the specific files, folders and data we need to synchronize from production server to a BCP server. * The installation of the system should be copied, although you can live without that if you're happy with a…
-
In theory, add another user to the database, and give it the correct rights. In reality, stop wasting your time thinking about it - you don't need or want to do it. You don't have any data in there you care about, and there's no point in using a different user, as there is zero benefit to doing it.
-
That's not going to happen on Cloud - it does not support any functionality that could pre-fill things. If you want to set a summary automatically, you have to do it in a post-function.
-
Next-gen projects do not (yet) support project leads.
-
None directly - you need to add the transitions "back" to each status, and then use add-ons to add conditions to stop your users performing the "wrong" transitions.
-
This will only work if you have done everything it says in the documentation. If you miss any step, or alter them away from the docs, it will fail. Which step did you skip?
-
The error seems clear to me - it's running out of memory. What are your users (including robots) trying to do at the time it fails?
-
Ahh, thanks @Johan Soetens _Dumblefy_ ! I will try to remember that!
-
No. Boards are not containers for issues, so there is no such thing as "move between boards". * If you want to have an issue that stops showing on a board when it changes status, then set the board filter to exclude the new status. * If you want to have an issue that starts showing on a board when it changes status, then…
-
Simplified workflows can be quite complex to get to, depending on your board and what it selects. You need to have the administrator click "simplify workflow" on your board, but the option will only appear if: * You have only one workflow across all the projects that the board filter selects for, so* all projects that…
-
Not easily. Delete really does mean delete - you've destroyed the issues in the database, the only thing left of them is a hole in the numbers and a line in the audit log. To get anything back, you'll need to restore a backup from before you deleted. As that will completely roll your system back, most people will restore…
-
Not quite - the system "component/s" field is multiple select naturally. Some of us disable that with code. But if you put multiple components on an issue, the "automatic assign" will pick the "first" component lead it finds amongst the components you've added. Defining "first" is a bit fuzzy - I can't remember what the…
-
There's no way to do this in Cloud. On Server, you could use the Behaviours module in ScriptRunner to inject the javascript that could do validation before submit, but Cloud does not support this sort of thing yet.
-
I'd take a guess that this is a "message field" from the Jira Toolkit add-on. That is still valid for Jira 7.x and should work the same way as it did in 3!
-
That's being done by whatever program you are opening the raw data in assuming every comma is a separator, not by the data. The only way to "fix" this on the Jira side is to rename the users without using commas in their names.
-
The status is not a field, so no. I don't think it's exposed directly in the REST API - you'd need to run a filter that returns a set of issues that are in all status in a workflow.
-
Jira does not support burning on sub-tasks, because it shouldn't happen in Scrum. In a scrum, you commit to doing a set of stories in a sprint. You burn down when the stories are done - there is no in-between - a story is either done or it is not. So the estimates on the sub-tasks are irrelevant. (This is not to say a…
-
What does the log say the server is doing?
-
This forum software often adds crud to the end of urls - remove everything from the first % onwards and try again.
-
Yes, if implemented correctly - only the base url needs to be redirected, so you can pull the rest of the url the user has landed on and just replace the base url part of it before redirecting
-
Ok, that answers it - that version is not supported by Jira 7.13. Try installing it on a supported database - see https://confluence.atlassian.com/adminjiraserver/supported-platforms-938846830.html
-
Sorry, I should have said to start looking in <confluence home>/log - the most likely place for warnings about permissions is in the atlassian-confluence.log file. My usual trick is to "tail -f" the log, so I can see what is being written to it in near real-time. Then in another window, attempt whatever is failing, and…
-
It's not particularly relevant how it got corrupted, but the most common causes I've seen for h2 failures are improper terminations of the server process (either a hard shutdown or something or someone killing it). But it also fails on running out of disk space, running out of memory, or even just coming under significant…
-
Use the "create meta" call to get a list of values - see https://developer.atlassian.com/server/jira/platform/jira-rest-api-example-discovering-meta-data-for-creating-issues-6291669/ (I don't use the JRJC, so I don't know if it supports it. I found it just gets in the way of me using the API properly)
-
But what version of MySQL is it? (Workbench is a client, not a server)
-
Re-check the permissions and restrictions on the space and page, and then if they still look like they should allow editing of the page for a user, read the log file to find out what is blocking it.
-
Your database is corrupted. In the short term, the fix is to install a clean development or test Jira (this is not a production system, obviously, as you're using the h2 database), and if you needed any of the data you were testing with, restore it from the last backup taken. In the longer term, switch to a supported…