Comments
-
Yes it is. It clearly states that "delete issue" is a project permission, and you don't need to give Jira admin rights to people if you want to let them delete. Could you have another look at the line that covers "delete issue" and the title of the section it is in?
-
Yes, when you apply a valid licence, all the functionality will come back.
-
As Adam said, "it could easily lead to an inconsistent experience for users" - this is a polite way of saying "most people do not want massive proliferation of windows or tabs forced on them, they want to have the choice you get from the right-click menu"
-
It is exactly what the message says - you should move to a supported database. The H2 database is ok for development and testing and firing up a quick starter system without having to delve into the database side, but it is unreliable and absolutely not suitable for production - it does not scale and it can (and does) fail…
-
Ok, you're asking this question in a place that is about Atlassian software, not Roku. Some of us might use it, but this is not a good place to ask. I'd suggest you ask in a Roku developer forum. My guess is that Roku use Confluence for documentation and you've clicked on a link for help with Confluence rather than Roku
-
Just to be clear, it does NOT do a Postgres export/dump, it exports all the data from the database to XML that Jira can read.
-
Jira Agile got turned into an "Application" and rebranded as "Jira Software". You now take a "Core" Jira installation and add the application via "manage applications" rather than add it as an App from the marketplace. Or, use the installer that bundles Jira Software with Core if you're starting fresh.
-
Your old licence may have been valid, but it only allows versions of Confluence to work that are released before the end date of the licence. You have upgraded past that end date, so the licence will not enable Confluence. You need to buy a new licence to enable this Confluence to work.
-
That's a new error, I assume you fixed the permissions one. This is telling you that the file you have tried to import is not XML
-
You would have to hack the templates that render the view screen to make them include custom fields.
-
You don't need to do any of that, and in fact, shouldn't, because you end up running a non-supported variant. Why are you not installing Jira as per standard instructions?
-
Yep, as I thought, your Jira server cannot reach itself over your network. You will need to work out what is blocking access and fix that.
-
You don't. You can only get to attachments via the issues, either in the web interface, or over REST
-
Can you wget the base url from the Jira server and get some html that shows the login page?
-
I'm afraid Jira has no support for that. It's not Scrum to burn down sub-tasks - either your deliverable story is done or it is not, so Jira doesn't do it.
-
Scriptrunner was written because Jira has no scripting functions. There are other automation and scripting apps, but you are going to need a scripting app of some sort.
-
Mostly. You will lose everything entered since the backup was taken, of course, and most Confluence systems have their attachments stored on the Confluence server, so if that was not backed up, you are going to lose them all too. (Some installations have attachments in the database, if you're one of those, then you will be…
-
Ok, this is a problem with your phone then, not Confluence. It must be sending the wrong thing to Confluence when you enter it. Is it possible you are mistyping something? I often get : and ; wrong when I'm trying to type on my phone.
-
What does "not able to login" mean? What are you doing, and what do you get back from the computers when you try to log in?
-
No cost, the developer licence is bundled with commercial licences (Academics and free licences don't get them)
-
Nope, it's Tomcat bundled in the installers, not Weblogic
-
I usually reach for Scriptrunner, because I know it quite well and have the experts who wrote it on tap
-
No, it's just the issue view affected.
-
Yes, the licence is purely a key that allows a number of users to use the system. It has no effect on the functions of the software beyond letting you use them (oh and the odd warning box for admins if the licence is expired or invalid)
-
>assume that my organization will not allow any add-ons You can't do it then. You need an add-on to provide the code, or a place to put the code for the post-function you need to use in the workflow.
-
Why? That would make the request pointless.
-
No, it will change the view a bit, but it won't change the layout that much.
-
No, you should not. An issue can only have one type. Having many issue types for an issue is nonsense and would break the system even if you did it.
-
It's in the database, but you should be able to change it by editing the connector. You'll need to put in a valid address for a single ldap server, without a protocol named.
-
This breaches your licence agreement. For the non production machines, use the developer licence that comes with the main one, the link is under the licence key in your my.atlassian.com account.