Comments
-
It is not clear what the "same fault" is on these. Could you confirm exactly what error you get when you try IMAP on port 993?
-
Does your Jira server have Software installed? (I know that sounds dumb, but it does matter). Log into it again and go to Admin -> Manage Applications. You should see a reference to "Core" and a second one for "Software" - do you see that?
-
What you need to do is line up the right settings. The server appears to be running IMAP and not POP. I say this because your question says it is responding with "OK The Microsoft Exchange IMAP4 service is ready", and then in your comment, you get "read timed out" when you try the other. So. You need to use IMAP settings…
-
See https://confluence.atlassian.com/doc/migrating-to-another-database-148867.html (I'm assuming you don't need to move the Confluence service, you are just migrating from Oracle to an AWS Postgres)
-
Ok, lets use the browser that is working, not the one with the XSRF problem. Could you go back to the my.atlassian.com account that you got the new licence from. That should list all your licences. Can you check exactly which product this licence is for?
-
Nothing. The emails are the same for all recipients.
-
This looks a little odd to me. Jira appears to be configured to try to connect to a POP mailbox, and it is reaching the mail server ok at first. But then it's getting responses that look like they are from an IMAP service. Jira supports both, but it can't work if you tell it to connect to one with parameters built for the…
-
Data Centre installs are a bit more complex than the Server systems they evolved from. Ignoring the DC stuff for a second - Jira needs a home directory to keep things in. We all refer to this as the "jira home". On server, this directory contains a load of directories and files Jira works with. Caches, attachments, working…
-
I have not seen any js hack for it since Jira 5, and that won't work now. I'm not aware of any plugins that do it either.
-
That's dreadful advice - reporting off a Jira database is the single worst way you can possibly approach it. As an example of just how bad an idea it is - could you give me the SQL query to fetch the data for one issue? It would be better to define where you are stuck and get advice from people who know Jira than to botch…
-
They went over the post-functions in the workflow, which will usually tell you which (missing) class is being called. Most add-ons give their classes distinct names which can tell you, or at least allow a web search for the name of the add-on
-
There's not a huge amount to do here really. I think all you need is to drop the lines about getting the project and issue, as the current issue is available already. So replace "MutableIssue issue = ... " because the object "issue" will already be the issue. But it is not a MutableIssue, so you'll need to cast it to use…
-
Yes, it is. You can transition an issue, which can poke your milestone system with a webhook.
-
Add functions to your website that poke the issues into Jira over the REST API. Or, try the "issue collector" function in Jira, that can save a lot of coding.
-
It's not 100% clear to me what you are trying to do here. If you mean you want to connect the 4 DR nodes to a new empty database completely separate to Production, but hosted by the same MS-SQL service, then yes. If you mean you want to connect DR to the Production database, then no, absolutely not. Unless your 4 DR nodes…
-
For "set up Jira", there are docs - https://confluence.atlassian.com/adminjiraserver/installing-jira-applications-938846823.html However, "from company website" might change the context, but I can't work out what it means, so I don't know. Please explain?
-
Oh gods, that's massively overcomplicating what an issue tracker is for. For the vast majority of people, the comments should be more than enough. When you're throwing vast amounts of conversations into an issue like that, it's time to put it in a proper documentation system, not some untracked threads. (Midway between…
-
Not quite, it's not saying you can't use it, it's saying you can't create another one with the same name. Try reusing the existing one with the right night.
-
Ohh, that looks like Jira can't write to the disk! Could you be out of space? (10 or 11 2Gb attachments will blow out your Cloud allowance for small-medium Jira systems) Although if it is Cloud, that should not happen, it should increase your allowance (and bill) automatically.
-
Not really, most Cloud users go to Confluence for questions, it's more natural in a system built for sharing generalised information rather than task-tracking.
-
Hmm, if the "jira" user is trying to run that and failing, then it's not the file permissions. Could selinux be blocking it all?
-
Workflows are not isolated entities. Each workflow is separate, but they draw on a common pool of status. So if you edit a status that several workflows are using, it's going to change for all of them, because they're all looking at the same thing. Similarly when you share workflows - if you edit it, you will affect all…
-
No. Not "mirrored". Just done. Boards are not containers for issues, they are a view of them. So you can include the same issue on different boards. It doesn't matter if you then change the issue via board 1, board 2, board 3, the issue view, the navigator etc, it is a change to the issue. So whereever it is appearing, it…
-
Go the your Jira dashboard (click on the Jira icon), then click Jira settings -> Issues -> Custom fields. That's the current list, with an "add" to the top right.
-
Mmm. Could you actually show us what the permissions are set to on a file that's failing?
-
Start at https://www.atlassian.com/software please . We're not here to do your work for you. (Although I'll save you a bit of time by saying: Jira Service Desk and Jira Software are applications you install on top of Jira Core. Everything else is a standalone service or an App for a product).
-
Yes. The recommendation is "be on the latest version of Jira Server before you export the data". There is some wiggle-room - when 7.9 was "latest", we did a direct 7.8 import ok, but there's no guarantee that even a small difference like that might not cause you problems or fail entirely. There's no chance of it working…
-
I suspect you've only made the directories owned by jira:jira The doc says you need to do the same for all contents within them. Try "chown -R jira:jira jira-directory", rather than "chown jira:jira jira-directory"
-
On Cloud, you're more restricted. I would have a look at Automation, and I think ScriptRunner can do it (but I don't think there are any Apps directly provide a function like this)
-
You'll need Apps to provide either a scripting framework, or to provide the listener itself that can do it.