Comments
-
You could try a VPN, but the best option is to find out how their system is "automatically re-directing to their own" - if we know how it's being done, we might have more possibilities for you.
-
Macros execute when you visit the page they are on - they're not suitable for scheduling or sending reports. It would be better to write a macro that provides the report you want and then ask the user to visit the page(s) you put it on.
-
The user that has been configured to talk to your LDAP system does not have the permissions in there to amend this Jira user's groups. You'll need to get the right permissions for the directory.
-
Could you explain what you want to start again with? If it Atlassian Cloud systems, then just get new ones and let the old ones lapse.
-
I am not trying to insult you, I am very sorry if it came over that way. It is purely my curiosity - you needed a web-server, why did you not use the one that is part of Jira? The one that Jira runs on, and is started by the startup scripts?
-
Ok, good, and all their sub-tasks (if they have any)?
-
You will need to debug the database connection, there's nothing else we can tell you. Can your Jira server reach the database server over your network? Can you log in with the credentials you are using for it? Can you try the mysql console on the Jira server to check the access?
-
>so I determined that tomcat required installation. I am sorry, that is utterly the wrong conclusion from what you've said, I don't understand why you would even begin to think that.
-
No, Cloud does not support functions like Behaviours.
-
You are right, it is the text field as described above - they're not "stattable". You're not doing anything wrong, the function isn't there. You could switch to a different method. Have a drop-down select list that you populate in listener code instead of a calculated field.
-
Do the issues that move have sub-tasks that are not also in the done column?
-
This will either be your anti-virus software throwing a false-positive, or it may be detecting malicious code someone has uploaded or added to it.
-
If you go to Admin -> Screen Schemes, you'll see the full list (and there is an expandable area at the bottom for the inactive unused schemes)
-
What documentation have you followed for getting the https working? Is it behind a proxy, or have you done it with just Tomcat? Have you set the base url in Confluence to the correct url? (Actually, do that first, as that's where the "base url" error is coming from, and in one case, it might simply fix the whole thing).…
-
That's a generic page-not-there error, it doesn't tell us what you were trying to do. Please could you tell us what the context is? What url were you trying to reach, or what did you click that took you to this?
-
It supports it natively, but you will have to build your own workflow for it. Should be simple as you can just list out the stages you want to go through and draw transitions from top to bottom.
-
Not text matching, it's simply using the last column that's on the right-hand side of the board! It's the "definition of done" to Jira Software
-
Are the "done" issues in the very last column of the board?
-
Are the issues in the right-most column on you board?
-
I'm not sure what you are posting for here, all you need is a download - Go to the Jira download page and download the most appropriate installer.
-
What do you mean by "pull the change", and why does it matter whether it is staging or local?
-
The REST calls in Jira are not defined by your authentication/access method. "does not support oauth 2" is nonsense.
-
Confluence pages are only deleted by humans, they don't just die without a human choosing to kill them
-
Odd, the shortened url you have there works fine for me, although it does land on https://confluence.atlassian.com/jirakb/jira-how-to-migrate-from-hsql-database-to-an-external-database-295308246.html when the shortening is resolved. The problem you have is that your system was installed with the hsql database rather than…
-
You will need to grant the permissions to read/write/run/delete to the user running your Jira service
-
Yes. Issue links link issues together.
-
This is quite hard to read as a question. You have two Jira systems and have customers appearing in both, as they're supposed to. Could you explain what is wrong?
-
Yes, that's because it is written to stop you going over the limit so you don't cripple your server. You need to put the limit into your REST call.
-
Yes, that is a very good question. I'm afraid the answer is that you need to build human systems that will make your humans curate the docs properly. That's not something you can build into software, as it needs humans to make choices about what to keep, update or throw away.
-
Look at the cost of a year's licence for 250 users. Subtract the cost of your current licence's months left.