Hello
I've a question about an old version of JIRA 4.0 build 466.
Does anybody know if that version would work with Exchange 2016?
I've been told it might not due to changes in Exchange no longer supporting MAPI over RPC. Although I believe JIRA 4.0 talks IMAP and exchange 2016 can still be configured for this.
Any advice appreciated.
It will, as long as Exchange is set up to allow IMAP (or POP3).
Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Wow.. JIRA 4.0 is soooo old :) .. I remember it clearly (it was a nice release), but most people from the community definitely did not even saw or work on JIRA 4.0. To answer that question and sleep well the only way is to do a simple test :) .. You can set up a TST environment and try connecting to Exchange (depends on what you want to achieve with this Exchange integration, but IMAP definitely should work as it is)
BTW - Is there something preventing from upgrading to the latest versions? :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Heh, I remember Jira 1.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Lack of money I believe is why it stopped being in maintenance and upgraded ; )
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@[deleted]- That is sad :( .. I hope that you follow on new features that might give someone an idea to buy a new license and upgrade (or start fresh since upgrade might be problematic)
@Nic Brough -Adaptavist-- Yeah, it is clearly more than 15 years ago.. It is a huge step from which Mike and Scott started up working on a new bugtracker and here we are .. on the community talking about...
BTW - Before JIRA 1.0 there was also 0.8.4 released :) .. Did you have a chance to install it? :) Wondering how the first official version looks like :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Nothing to do with money - maintenance on 1 stopped because 2 was released!
My Atlassian journey started when I was handed an active Jira 2.7.3 and was asked to look at upgrading it, starting with a recommendation on version. 3.0.0 was released the week I started that. We settled on 3.0.3 eventually, and the next project was merging a 1.something install into it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.