Comments
-
We'll try, but we don't know where to start. You've said you've "read about it", but have not told us what you have read, or where you are stuck. For the versions you've mentioned, I'd upgrade to 6.4, then 7.0, then 7.1.latest, but I can't really tell you more without knowing why you say you can't do it.
-
Please, read the answers you've already been given here.
-
Ok, then no, you don't need to renew to upgrade to 6.3, the last version was out at the beginning of this month.
-
We can't tell from the SEN (We're not Atlassian, we're end users like you) but you probably do to renew the licences. Your licence entitles you to use (and upgrade to) any version of Jira released before the END of the licence period. If your licence expired before 6.3 was released, you can NOT upgrade to it. So the…
-
Ok, that's not really a good enough reason to use it, but the fact is that there are bugs in the product that break Confluence. You need yubikey to fix their software, or tell you what you've got wrong in the configuration of it.
-
The add-on is providing some security that Confluence doesn't do off-the-shelf. I assume you have good reasons for using it, but the answer has to be "if it breaks things you need, then turn it off" (Part of me wants to say that most of the security Confluence does do is fine, but I do know I am missing scenarios where it…
-
My guess is that your project team members do not have the global "browse users" permission.
-
Or someone else who has admin on that space.
-
That's not a workaround - there is no "evaluation copy", you're using the installed one that you could have added via the marketplace.
-
You don't download a licence, you get the key in the licence page on the my.atlassian.com account and paste it into the licence box once Agile is installed. Justin is correct about where and how you "download" the plugin - go to "manage addons" in admin and look there. If you have the plugin installed, it will be there,…
-
You need to protect the workflow transitions with "conditions". The default is to put no conditions on new transitions, and that catches out a lot of us when we create them. You need to edit every workflow and add something like "must be in the role of users" or "must be in the role of developers" This changes in…
-
If they're free, they're enabled, if they're paid, go to your OnDemand account and buy them. If they're not on the list of supported plugins, then you can't. See https://confluence.atlassian.com/display/AOD/Atlassian+OnDemand+Plugin+Policy
-
Yes, it's been removed, apparently, you don't need it any more on Cloud. (I questioned that, as there's stuff on it I always find useful, but haven't heard anything back yet) Maybe raise it with support? See if you have better luck than me?
-
You do need to install the ZAPI add-on as well as Zephyr.
-
How are you storing these test cycles in JIRA?
-
No, but yes. Screens (like many other things) are configured by project and/or issue type. You can mix and match whatever screens you want across different issue types and projects. The one thing you can NOT do (because it's pretty much nonsense and if needed, means you've got a broken process) is have an issue type in a…
-
... votes ... I think it's immensely clunky to start messing around with function names with prefixes and subscripts. Keep them simple and flexible. But having a help text available while you're trying to work out what you're doing is a really good way to solve the problem. Users can be informed exactly what they're doing…
-
>but I believe this only sets the variable for this session, for me. Is this true? Yes. But if you add it to the file .bashrc it will run every time you log in automatically (assuming you use bash as your shell - it is the default for most of the more popular distros) Similarly, you can add it to the scripts you use to run…
-
This is not a forum for Visual Composer, it's for Atlassian applications. I suggest you ask in a VC forum.
-
Or a database backup - those are better for medium to large installations...
-
No. Your installation is your own, it can only be accessed by the people you've given accounts to (There's three there - Jira user accounts, some of which will have admin rights, server accounts and database accounts). If you've given Atlassian one of those, then that's fine, but they wouldn't do this to any client. It's…
-
It doesn't matter what you want to change, you have to get a new one, as described above.
-
No. I really do mean cannot change.The only way to get a Cloud installation to run on a new URL is to create a *new* Cloud instance, export all your data from the old one, import it into the new one, and then (optionally) delete the old one. That is NOT "change", that is "Create new and delete old". Atlassian won't change…
-
You cannot change the url of an Atlassian Cloud installation, so there is no reason to let you change the base url either (all it would do is break the application).
-
Yes, they set up the network routing and proxies as described in the accepted answer.
-
Ok, so if you can hit http://192.168.0.20:8090/confluence from 192.168.0.20, but not anywhere else, then you have a firewall on that machine blocking external access. You need to find that and open up the port (the /confluence is not important)
-
Good, we're getting there. As you want "can see confluence's basic stuff, but must log in to see the rest", that's probably working (And even if it's not right, it's just a case of looking at space permissions to ensure none of them say "anonymous") So, next quick diagnostic questions/confirmations: * You can see…
-
You will have to expose some of Confluence on the server in order for people to log in. The computer can't know whether a user is allowed in until it knows who they are. That means you want a public Confluence (in network terms), but not anonymous (so that people can find it, see the login stuff and log in if they have an…
-
I know it was a joke, but it did imply that you've changed some setting in JIRA!The thing is, something somewhere *has* changed. You weren't getting an error and now you are. Either the emails have changed format, or there's a change of settings in JIRA that causes this.My best guess is that the target project has had a…
-
I'd suggest changing the "time to tear your hair out" option back to what it was before. I'm afraid the error message is too vague to tell us what is going on - we can tell that an email arrives and it's not handling something in there, but all we can really do is ask you to check the config for the mail handlers is valid.…