Changes to Atlassian products

[Giovanni Tirloni]

Hi Justin,

I looked for the plugins in the marketplace but I was only able to install the following:

[cid:5e432dbf-49eb-4087-8970-42bbf7bf170b]

We'll probably have to re-apply to get open-source licenses for them since they're paid.

Additionally, I couldn't find a way to transfer our existing licenses over to the cloud installation. It seems each plugin installed gets a new license number that can't be changed.

I think it's very likely we'll face some disruption in functionality.

---

I was re-reading the FAQ<https://www.atlassian.com/migration/faqs> about this change in Atlassian's policy and it says the following:

Server customers will have access to maintenance and support for an additional three years, ending February 2, 2024 PT

So, I'm thinking that if they will provide maintenance and security updates until 2024.... we don't really need to make this migration right now.

My initial reading of the situation was that they would halt all development in February 2021 but that doesn't seem to be the case.

________________________________
From: Justin Obara <obara.justin at gmail.com>
Sent: Monday, November 9, 2020 22:18
To: Giovanni Tirloni <gtirloni at ocadu.ca>
Cc: fluid-work at lists.idrc.ocad.ca <fluid-work at lists.idrc.ocad.ca>
Subject: Re: Changes to Atlassian products

Hi Gio,

Thanks for working on this. It’ll help us get used to the new URLs and etc. I think the timing is fine, but you should probably warn the AIHEC group. Not sure, how to get a hold of them though, maybe through Jutta?

Will we be losing any functionality, e.g. plugins that aren’t supported anymore?

Thanks
Justin

> On Nov 9, 2020, at 6:00 PM, Antranig Basman <antranig.basman at colorado.edu> wrote:
>
> I like the idea of the redirects + load balancer and for me, given I am now a family man, the weekend is a perfectly fine time for that migration work. Thanks so much for looking into it!
>
> Cheers,
>
> Antranig
>
> On 09/11/2020 22:51, Giovanni Tirloni wrote:
>> One alternative that I've been researching is to migrate JIRA/Confluence to the cloud and keep a load balancer on our infrastructure doing the HTTP redirects.
>> issues.fluidproject.org/$1 -> fluidproject.atlassian.net/$1
>> wiki.fluidproject.org/$1 -> fluidproject.atlassian.net/wiki/$1
>> I think this would be a viable solution and could give us more time to plan a migration to some other system if desired.
>> To work on that, I need to shut down the wiki/issues websites while the migration is happening. Would this weekend be a good time to work on that? Any concerns?
> _______________________________________________________
> fluid-work mailing list - fluid-work at lists.idrc.ocad.ca
> To unsubscribe, change settings or access archives,
> see https://lists.idrc.ocad.ca/mailman/listinfo/fluid-work

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idrc.ocad.ca/pipermail/fluid-work/attachments/20201110/0c10870d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 26098 bytes
Desc: image.png
URL: <http://lists.idrc.ocad.ca/pipermail/fluid-work/attachments/20201110/0c10870d/attachment.png>