We wanted to let you know that we’ll be transitioning to a new support service during this week.
Ooops! You probably figured that out if you received an email from my Sandbox testing a few minutes ago…
I forgot to turn off a ‘Welcome’ email flag on the sandbox system when I was testing the user transfer routine – sorry about that.
You will get another one from the “live” user transfer shortly [without the SANDBOX as it were].
Why are we doing this?
It’s partly about time-saving so we can handle your questions and problems faster; that plus improved ticket tracking, analytics, and being able to support multiple channels of communication from a single source. Web, Email, Twitter, Facebook will all be connected.
Yes, you can use multiple identities; multiple email, twitter, etc. and see everything under your one account. You can now do voting on community suggestions, questions and topics. The search is vastly improved (IMO) over the previous support system. You can enter your post using a text-editor that doesn’t require knowledge of Markdown to do simple formatting.
There’s a bunch more — and we will do some more customizing over the next few weeks to add even more features. And we’ll be putting more up-to-date knowledge base information into the system in the coming days as well.
What does this mean for you?
You’ll be asked to verify your email address and create a new password when you login for the first time. Wish there was a way around this, but it’s a one-time thing that we hope you won’t find too onerous.
What about all of the great posts on the existing forum?
We’ll be leaving the existing help.nirvanahq.com in place for a few weeks as there is a wealth of information and great discussions here, but please start all new forum discussions and support requests over at support.nirvanahq.com.
We are looking at ways to preserve some of the more interesting discussions here, either by importing them into the new system, or as an evergreen archive that can be referenced to some other way.
We know there will be some transition pain getting used to the new system, but I think we all will benefit going forward.
N2 Build 389 brings some minor but nifty additions.
- Links to evernote:// within task notes are now clickable
- Added some more font choices (calibri, tahoma, verdana…)
N2 Build 390 fixes a bug that was introduced in Build 389 where changes made on one device was not being reflected in the UI of other devices. Changes were being posted to the cloud just fine, but we’d botched the timestamp persistence in the local cache so changes from the cloud were sometimes being ignored.
NOTE: you must logout and then login for the Build 390 fix to take effect. (Local cache gets cleared on logout, and then rebuilt on login.)
QUICK FIX: N2 Build 391 fixes a rare edge case where a repeating task could yield spawned tasks named (untitled) on save … also related to timestampage that we missed in build 390.
File this post under technical fyi / cya / wtf.
For the past few weeks we’ve been working out the kinks in our server-side processing of large data sets relating to scheduled and recurring tasks, which has affected a small but significant subset of users.
In a nutshell, prior to build 358, N2 relied on each client (desktop/mobile browser session) to process nightly task movement locally, and then post any changes (scheduled to next, next to focus etc) to the cloud. Since build 358 the primary responsibility for processing tasks has been moved back to the cloud, which then pushes changes out to the client. Role reversal.
The initial worker scripts we wrote to do all of this processing were a bit over-zealous in their consumption of memory. Kinda saw this coming, and to preempt it being a show-stopper we added some client-side code to detect if there are tasks that should have been processed but weren’t, with a “manual override” that conditionally appears in your Scheduled and Focus lists if relevant.
The appearance of the buttons “Move Scheduled Items Into Place Now” or “Bring Focus Up To Date Now” is N2’s way of letting you manually invoke the routine that moves tasks into place locally, without waiting for the cloud to do the processing. In an ideal world, you would never see these buttons as everything should be automatic. But you know… it’s like when the automatic doors don’t open when you walk up to them, at least you can still push ‘em open to get through. Or something like that.
I’ve been up all night monitoring and adjusting the worker scripts, and it looks like things are finally working as intended. But for folks in timezones GMT +1 ,0, -1, -2, -3, -4, -5 and -6 (ergo, the 8 hours preceding this post) you may see the “Bring Focus Up To Date” button. Just click it if you see it and you’re good to go. Also, if you’re in the aforementioned time zones you may not have received your daily email poke today. Sorry about that.
Will continue to monitor things for awhile, and if things continue to look good we’ll be able to put this issue behind us and move on… to more fun things that all this server-side processing makes possible, like calendar feeds and the like. :-)
We’ll be moving some things around this evening. We don’t anticipate any interruption of service, though you may notice some slight sluggishness in site response from time to time, or not. :-)
Will post progress on twitter @nirvanahq
We’ve been running the latest builds in Internet Explorer 9 for a few days now and, gosh darn it, I think we did it. We have N2 working in IE9 without chrome frame! (and it’s surprisingly snappy too)
I was worried for awhile there that we weren’t going to pull this off, which would have meant leaving a significant group of N1 fans—those poor souls who are restricted to using IE at work without admin rights to install anything—stranded after the cutover to N2. This pool is larger than you might think, and it would definitely have had an impact on our ability to gain wide adoption post launch.
It’s looking like we may get IE8 working too, which would be awesome.
For the geeks: Server-side we had work to get the api exposed via the same subdomain as the app, as IE’s default settings block cross-origin resource sharing. Client-side, well, we all know the joys of getting things to render reliably with any level of precision when you’re trying to support the full array of browsers, let alone pushing the envelope of html5 and jquery.
There are a bunch of bug fixes (UNL and Waiting-related, among others) and we added a few nice new features (multi-select-right-click being a big one). Barring any last minute hiccups, we expect to roll this out over the weekend.