Bugs in 1.0?
 

[QUOTE=BwanaZulia;33250]After all these pages, the one true answer to the question is "Because it can be." Obviously people are willing to buy it and obviously OmniGroup has put in a lot of time developing it and needs to both recover cost and do further development.[/QUOTE]

Yes, but at the end of the day when all those people buy it if they start finding all the bugs how likely are they going to be to recommend it to others or to purchase upgrades. I really hope they release 1.0.1 quickly and quash a bunch of these bugs but since they have publicly stated that they already have plans for at least two minor revisions 1.0.1 and 1.0.2 it seems pretty obvious that even some of the more obvious bugs won't be fixed for a while.

[QUOTE=frankly;33253]Yes, but at the end of the day when all those people buy it if they start finding all the bugs how likely are they going to be to recommend it to others or to purchase upgrades. I really hope they release 1.0.1 quickly and quash a bunch of these bugs but since they have publicly stated that they already have plans for at least two minor revisions 1.0.1 and 1.0.2 it seems pretty obvious that even some of the more obvious bugs won't be fixed for a while.[/QUOTE]

All the bugs? I haven't found OmniFocus to be particularly buggy, and I use it a lot. Sure, there are a few niggling issues, but overall it's a pretty solid 1.0 release (as good or better than most 1.0 releases). Also, be careful to separate fixes from enhancements. A desired new feature is [I]not[/I] a bug.

I would (and have) whole-heartedly recommended OmniFocus to others.

Also remember, while it is a 1.0 release, they gave you 1.0 pre-price, so you are not paying full price for the 1.0 (or shouldn't have).

As a daily user, I don't see to many bugs, if any. I would love more features, but I know OG and they are coming.

BZ

[QUOTE=BwanaZulia;33258]Also remember, while it is a 1.0 release, they gave you 1.0 pre-price, so you are not paying full price for the 1.0 (or shouldn't have).

As a daily user, I don't see to many bugs, if any. I would love more features, but I know OG and they are coming.

BZ[/QUOTE]

That has already expired as noted by Ken in one of his responses. Thousands of people have already paid full price.

Bugs in 1.0?
 

[QUOTE=Toadling;33254]All the bugs? I haven't found OmniFocus to be particularly buggy, and I use it a lot. Sure, there are a few niggling issues, but overall it's a pretty solid 1.0 release (as good or better than most 1.0 releases). Also, be careful to separate fixes from enhancements. A desired new feature is [I]not[/I] a bug.

I would (and have) whole-heartedly recommended OmniFocus to others.[/QUOTE]

I am a software developer so I am careful and know that I am talking about bugs. Also, is the bar so low that we expect bugs in a 1.0 release? What are alpha and beta releases for if not to get rid of these things before releasing into production? I know that you can't get it perfect on the first try but when I developed software if a bug were found that was affecting the use of the application we didn't add it to a list of bugs and plan to release all the fixes at once. We fixed it, tested the fix, and deployed it. This idea that they have all of these bug fix releases planned tells me they know about a bunch of bugs and are taking a good amount of time to fix them. Once people invest money in your product I think they deserve fast service. How about a reply from support within 24 hours at least?

Know bugs acknowledged by Omni in the forums:
[url]http://forums.omnigroup.com/showthread.php?t=6722[/url]

I've only been using it for a few days and have found the following:

1) Checking the Show Soon and Overdue actions in the menu bar and Dock would not work. Then all of a sudden the next day they started working.
2) Even though you tell it to sort things by due date they don't sort. I currently have items sorted by due date and OmniFocus has them ordered like this: 2/29, 2/21, 2/26. How in the heck can you get organized if you have items that are due today displayed below items that are due next week?

I'm sorry but things like this that make you waste your time trying to figure out why they don't work is ridiculous, especially from a piece of software whose main function is to help you save time and get things done!!!

[QUOTE=frankly;33262]Also, is the bar so low that we expect bugs in a 1.0 release?[/QUOTE]

No, I don't expect glaring bugs in a 1.0 release. But, in reality, a software developer such as yourself (and many others on these forums) should know that releases, particularly 1.0 releases, are often under enormous pressure in both time and resources. So while I don't like to see bugs, the simple fact of the matter is that it's not unusual to see a few in the first release. As a software developer, have any of your 1.0 releases been entirely bug-free? Heck, have [I]any[/I] of your software releases been entirely bug-free? If so, you are truly a gifted developer and in the extreme minority.

[QUOTE=frankly;33262]What are alpha and beta releases for if not to get rid of these things before releasing into production?[/QUOTE]

Having participated in the alpha and beta programs, it seems to me that the vast majority of reported major faults were fixed in those iterations. Others bugs still exist (with arguably minor impact), but at some point you just have to ship the product.

[QUOTE=frankly;33262]I know that you can't get it perfect on the first try but when I developed software if a bug were found that was affecting the use of the application we didn't add it to a list of bugs and plan to release all the fixes at once. We fixed it, tested the fix, and deployed it. This idea that they have all of these bug fix releases planned tells me they know about a bunch of bugs and are taking a good amount of time to fix them.[/QUOTE]

You don't follow a planned release cycle for your products, where bug fixes and features are accumulated and released at periodic intervals? It sounds like you deploy a new release for each and every fix. Isn't that inefficient?

I think Omni's approach is more typical in the industry. I know it's certainly the process in my company, but then we're a much larger operation than OmniGroup with over 70 developers working on a single product.

As for having releases mapped out into the future, have you considered that some of the included fixes might just be very complicated and require more time to get right? Or maybe they're dependent on an OS-related bug that first needs to be fixed by Apple. In those cases, it makes sense to plan smaller releases in the interim to get at least some of the fixes out into the field, then release others later. I don't see a problem with this. In fact, it suggests that Omni is doing a good job prioritizing fixes and planning their release cycles - exactly what I'd expect from an organization of professional software engineers that follow a process.

Anyway, it's only a been a little over a month since OmniFocus 1.0 was released. A week or two of that time was surely consumed by Macworld. That leaves 4 weeks or less since the initial release. That doesn't seem like very long at all.

[QUOTE=frankly;33262]Once people invest money in your product I think they deserve fast service. How about a reply from support within 24 hours at least?[/QUOTE]

And for the most part, I think Omni Group customers do get fast service. That's one of the things Omni Group's reputation has been built on. I'd dare say few consumer software companies offer better service on such a large scale.

But to expect 24 hour response times is pretty demanding. I can't think of any consumer software companies that guarantee 24 response times across multiple products without the customer having to pay for a special service agreement.

[QUOTE=frankly;33262]I've only been using it for a few days and have found the following:

1) Checking the Show Soon and Overdue actions in the menu bar and Dock would not work. Then all of a sudden the next day they started working.[/QUOTE]

I haven't seen this problem, nor have I read any reports of it here before now. Are you able to reproduce it? If not, there's insufficient information here for Omni to even start thinking about a fix. Still, if you're interested in participating in the community, you could send feedback about it to Omni and then keep an eye open for the issue to reoccur in the future.

[QUOTE=frankly;33262]2) Even though you tell it to sort things by due date they don't sort. I currently have items sorted by due date and OmniFocus has them ordered like this: 2/29, 2/21, 2/26. How in the heck can you get organized if you have items that are due today displayed below items that are due next week?[/QUOTE]

Are you sorting in Planning Mode or Context Mode? Note than sorting works on projects in Planning Mode and on actions in Context Mode.

FWIW, I haven't seen any sorting problems on my system. But if you still see this problem, I'd encourage you to discuss it openly on these forums (there are lots of smart people here with deep knowledge of OmniFocus) and send feedback to OmniGroup if you're convinced there's a bug.

[QUOTE=frankly;33262]I'm sorry but things like this that make you waste your time trying to figure out why they don't work is ridiculous, especially from a piece of software whose main function is to help you save time and get things done!!![/QUOTE]

I'm sorry you feel like you're wasting your time. And there's no doubt that OmniFocus is a sophisticated app that can sometimes be confusing if you aren't familiar with it. And I'm sure there are some bugs that have yet to be worked out or even revealed. But from the examples you've given here and my own experience, I don't really see a significant problem.

1) I love how you question me about how many releases have been bug free, completely ignoring the subsequent paragraph (which you later quote) that states the approach I took when bugs presented themselves. Don't cherry-pick my posts. It doesn't help to further the conversation.

2) "but at some point you just have to ship the product." ????? Really??? They weren't delivering this to an outside client. They are under NO OBLIGATION to ever ship this product. The only obligation they have is to themselves. If this is your attitude toward software development then you WILL release buggy code.

3) Again, it helps if you actually read what I wrote. I did NOT say that we didn't follow a planned release schedule. What I DID say is if a bug were found that was affecting the use of the application we didn't add it to a list of bugs and plan to release all the fixes at once. We fixed it, tested the fix, and deployed it.

Let me repeat, if a bug were found that was affecting the use of the application we didn't add it to a list of bugs and plan to release all the fixes at once. We fixed it, tested the fix, and deployed it.

There are different levels of bugs to be sure but the one I mentioned about the sorting order is NOT one that I would let wait to be grouped with other fixes.

4) You may not be aware of any examples of exemplary customer service but that does not mean they don't exist. I deal with many companies that provide fast responses and they DO NOT require extra money in order to do this. Heck, Jet Brains (makers of IntelliJ IDEA) actually respond to queries in less than 30 minutes on EVERY occasion that I have asked them a question. Yes, less than 30 minutes.

5) So let me get this straight, the INTENDED function is that actions should not be sorted inside of projects? I suppose if that is how they INTENDED for it to work then it isn't a bug. It doesn't make any sense to me that it would work that way but I didn't create the specification for this product.

6) It is a waste of time, no matter who you are, to work through bugs just to be able to use a piece of software. Unless you are a paid tester then it is by definition a waste of your time. I'm not sure why you would have a problem with that statement.

I am inclined to agree about wanting to sort items by due date in planning mode.

I have a Next Actions Single Actions List and if I could sort them by due date I could find out which is the next due Action and its Context and move myself to working in that context if at all possible

[QUOTE=Dogsbreath;33267]I am inclined to agree about wanting to sort items by due date in planning mode.

I have a Next Actions Single Actions List and if I could sort them by due date I could find out which is the next due Action and its Context and move myself to working in that context if at all possible[/QUOTE]

That's a good suggestion, something Omni should seriously consider implementing. But it's not a bug.

As it is, I believe the feature is working as intended: sort by project in Planning Mode and by action in Context Mode. You may or may not agree with that design decision, but that's what was intended and I'm pretty sure that's what we got. Am I wrong?

[QUOTE=Toadling;33271]That's a good suggestion, something Omni should seriously consider implementing. But it's not a bug.

As it is, I believe the feature is working as intended: sort by project in Planning Mode and by action in Context Mode. You may or may not agree with that design decision, but that's what was intended and I'm pretty sure that's what we got. Am I wrong?[/QUOTE]

I always love the "working as intended" line. If I code something to specs and it doesn't make any sense for it to work that way then yes, it is not a bug. But if it doesn't make sense for it to work that way it should have been caught during the planning process of the application. Maybe I'm wrong. Maybe only Dogsbreath and I have an issue with this. But it seems absolutely illogical that I would want to sort projects by due date and NOT have the actions inside of those projects ALSO sorted by due date.

[QUOTE=frankly;33272]I always love the "working as intended" line. If I code something to specs and it doesn't make any sense for it to work that way then yes, it is not a bug. But if it doesn't make sense for it to work that way it should have been caught during the planning process of the application. Maybe I'm wrong. Maybe only Dogsbreath and I have an issue with this. But it seems absolutely illogical that I would want to sort projects by due date and NOT have the actions inside of those projects ALSO sorted by due date.[/QUOTE]

OK, that's great. Those are good suggestions for improving the product. Were you involved in any of the deep discussions on these forums during the alpha and beta programs? Did you send your suggestions to Omni Group with the Feedback menu option? If not, please do!

But I still don't see much evidence of a significant number of "obvious bugs".

[QUOTE=frankly;33266]Let me repeat, if a bug were found that was affecting the use of the application we didn't add it to a list of bugs and plan to release all the fixes at once. We fixed it, tested the fix, and deployed it.[/QUOTE]

We identified the bugs in that Known Issues thread after we shipped 1.0. We immediately started working on fixing them, but we also posted those known issues to the forums to let people know about the problems rather than just pretending they didn't exist until we fixed them. (Some have already been fixed in the 1.0.1 sneaky peeks, but some people aren't testing those beta releases and we still want them to know about the issues.)

[QUOTE]You may not be aware of any examples of exemplary customer service but that does not mean they don't exist.[/QUOTE]

We do try to reply to all support email within one business day, and for most of our products we've usually done much better than that (sometimes replying within minutes, frequently within hours).

Unfortunately for our support team, OmniFocus has been incredibly successful, with a product launch that far exceeds anything we've had for any of our other products. So even though we pre-hired two support people specifically to handle OmniFocus support email before we launched, they've still been overwhelmed—which is why we're [URL="http://blog.omnigroup.com/2008/01/25/support-ninja-gig-available/"]hiring more[/URL]. Hopefully we'll be back to our usual standards soon. (And we certainly won't be satisfied until we are!)

[QUOTE]5) So let me get this straight, the INTENDED function is that actions should not be sorted inside of projects?[/QUOTE]

Yes, that's correct: we assume that the order of actions in a project is important, and so we never change that order in planning mode. (It can represent the dependencies in a sequential project, or the priorities in a parallel project.) It's easy to reorder actions if you want them in a different order, and we do offer the ability to select actions within a project and sort them manually (using the Sort submenu in the Edit menu).

[QUOTE=Ken Case;33275]Yes, that's correct: we assume that the order of actions in a project is important, and so we never change that order in planning mode. (It can represent the dependencies in a sequential project, or the priorities in a parallel project.) It's easy to reorder actions if you want them in a different order, and we do offer the ability to select actions within a project and sort them manually (using the Sort submenu in the Edit menu).[/QUOTE]

When you put it that way it does make sense for a great deal of projects. I also appreciate the option to sort via the Edit menu. However, the sort options available via the Edit menu (By Name, By Date Added, By Date Completed) don't help. Is there a possibility we might see By Due Date added here? Date Added doesn't seem all that helpful. The nature of the way you suggest using OmniFocus is that you are just brain dumping tasks into it as opposed to thinking about it where the Date Added would come in handy. And Date Completed is only useful if you are viewing all items.

Am I the only one who has some of his "projects" as todo lists for certain ongoing projects? That is really why I need to sort the action items by due date within a project.

[QUOTE=frankly;33276]However, the sort options available via the Edit menu (By Name, By Date Added, By Date Completed) don't help. Is there a possibility we might see By Due Date added here?[/QUOTE]

Yes, this is planned for 1.1.

[QUOTE]Am I the only one who has some of his "projects" as todo lists for certain ongoing projects? That is really why I need to sort the action items by due date within a project.[/QUOTE]

That's perfectly reasonable; the way I do this is to use the Due Items perspective, which switches over to context mode and groups all my actions by their due date.

If you'd like to focus on a particular project while you're in context mode, you can click on an action from that project and select "Focus on [project]…" from the View menu.

Hope this helps!

[QUOTE=Ken Case;33280]Yes, this is planned for 1.1.



That's perfectly reasonable; the way I do this is to use the Due Items perspective, which switches over to context mode and groups all my actions by their due date.

If you'd like to focus on a particular project while you're in context mode, you can click on an action from that project and select "Focus on [project]…" from the View menu.

Hope this helps![/QUOTE]

Thanks for the suggestions. Interestingly I am still seeing some sorting issues. I did exactly as you suggested but down in the Due within the next month section the actions were not sorted correctly. I have one due on 3/18 that is showing up before one due on 3/4.

Frank

[QUOTE=frankly;33266]1) I love how you question me about how many releases have been bug free, completely ignoring the subsequent paragraph (which you later quote) that states the approach I took when bugs presented themselves. Don't cherry-pick my posts. It doesn't help to further the conversation.[/QUOTE]

Actually, if you go back and reread [i]your[/i] post, you'll see the relevant text was all in a single paragraph. I didn't quote anything from your second paragraph.

Your first paragraph implies that you expect [i]no bugs[/i] in a 1.0 release.

You said:
[i]"Also, is the bar so low that we expect bugs in a 1.0 release? What are alpha and beta releases for if not to get rid of these things before releasing into production?"[/i]

You then go on to write: [I]"I know that you can't get it perfect on the first try but when I developed software if a bug were found..."[/I].

Here you now acknowledge that it's difficult to have a bug-free first release, which is in seeming contradiction to your earlier implication. And then you also qualify your own experience with "...[i]if[/i] a bug were found...".

These implications, seeming contradictions, and qualifications left me unclear as to your meaning. So I think my original quesiton was legitimate: "Have you ever shipped bug-free software?"

From your more recent post, I take it now that you haven't ever shipped a release without bugs, which was my point all along.

[QUOTE=frankly;33266]2) "but at some point you just have to ship the product." ????? Really??? They weren't delivering this to an outside client. They are under NO OBLIGATION to ever ship this product. The only obligation they have is to themselves. If this is your attitude toward software development then you WILL release buggy code.[/QUOTE]

Of course they were delivering OmniFocus to an outside client: us!

And Omni certainly made an obligation to ship the product when they set the official release date and started accepting payments ahead of time! Even before that, there was an implicit obligation made by Omni Group by simply announcing that they were working on the application, discussing it openly, and inviting people to participate in the alpha and beta programs. Thousands of customers were sincerely *expecting* a release in the not-too-distant future!

But if we follow your reasoning, does any software company really have an obligation to anyone other than themselves? No matter who your customers are, corporate clients or home computer enthusiasts, if you let them down, they will eventually stop buying your products and the company will go out of business. The obligation, in its simplest form, is to stay in business and make money. Omni Group is no different from any other software development house in that respect.

[QUOTE=frankly;33266]3) Again, it helps if you actually read what I wrote. I did NOT say that we didn't follow a planned release schedule. What I DID say is if a bug were found that was affecting the use of the application we didn't add it to a list of bugs and plan to release all the fixes at once. We fixed it, tested the fix, and deployed it.

Let me repeat, if a bug were found that was affecting the use of the application we didn't add it to a list of bugs and plan to release all the fixes at once. We fixed it, tested the fix, and deployed it.

There are different levels of bugs to be sure but the one I mentioned about the sorting order is NOT one that I would let wait to be grouped with other fixes.
[/QUOTE]

OK, no need to get snarky. You didn't say that you didn't follow a planned release schedule. You also didn't say that you did. Let me clarify my question:

So, you fix it, test it, and deploy it. What does "deploy" mean in this case? Ship to a customer? If so, are you shipping each fix individually? Or do you accumulate multiple fixes into a point release and ship that to customers at planned intervals? I think most software shops do the latter, including Omni Group. But it sounded like you were advocating the former, no?

[QUOTE=frankly;33266]4) You may not be aware of any examples of exemplary customer service but that does not mean they don't exist. I deal with many companies that provide fast responses and they DO NOT require extra money in order to do this. Heck, Jet Brains (makers of IntelliJ IDEA) actually respond to queries in less than 30 minutes on EVERY occasion that I have asked them a question. Yes, less than 30 minutes.[/QUOTE]

That's great, Jet Brains sounds like they have good customer service. I hadn't heard of them before and I've never used any of their products. But I can't think of any other companies that guarantee 24 hour response time (without additional service contracts). Sometimes you might get a response in 24 hours, but it's not guaranteed.

But that's not to say I haven't had exemplary customer service on many occasions from lots of software companies, some even within 30 minutes of my original request. Heck, I bet even Omni Group has at times responded to a customer in under 30 minutes.

But I still think expecting a guaranteed 24 hour response *all* the time without a special service contract in expecting too much and unrealistic. If you can find it, great. Enjoy.

[QUOTE=frankly;33266]5) So let me get this straight, the INTENDED function is that actions should not be sorted inside of projects? I suppose if that is how they INTENDED for it to work then it isn't a bug. It doesn't make any sense to me that it would work that way but I didn't create the specification for this product.[/QUOTE]

Did you participate in any of the discussions of this very topic in the alpha or beta programs? If not, I strongly urge you to do a search of the forum.

Ultimately, it was decided that Planning Mode should be project-oriented and Context mode should be action-oriented. So each mode sorts its items accordingly. Sorting actions independently in Planning Mode is troublesome when everything is presented inside projects.

Note that you can also right-click a selection of actions inside a project and choose a manual sort order, but Due Date is not currently among the options.

Again, if you have strong feelings about this or good ideas on how things can be improved, I urge you to start a thread and state your case. And be sure to send your ideas to Omni Group via the Help->Send Feedback... menu item.

[QUOTE=frankly;33266]6) It is a waste of time, no matter who you are, to work through bugs just to be able to use a piece of software. Unless you are a paid tester then it is by definition a waste of your time. I'm not sure why you would have a problem with that statement.[/QUOTE]

I don't have a problem with that statement. I don't want to have to sort through serious bugs anymore than any other paying customer.

But didn't you just acknowledge that this sorting issue was [i]not[/i] a bug? And your only other bug report was non-reproducible, wasn't it?

So what other bugs are you wasting your time on? I'm not trying to be facetious. I'd really like to know, because I've not encountered any real problems. I do have a list of small issues, but nothing that really wastes my time. I make a note of it, send feedback to Omni, and occasionally discuss it here.

It was almost fun, seeing Omni listening to the feedback and fixing issues all throughout the alpha and beta phases. This has maybe slowed down a bit since the final release, but there's still regular activity in the sneaky peak builds.

[QUOTE=frankly;33281]Interestingly I am still seeing some sorting issues. I did exactly as you suggested but down in the Due within the next month section the actions were not sorted correctly. I have one due on 3/18 that is showing up before one due on 3/4.[/QUOTE]

By default, the "Due" perspective groups actions by their due date but doesn't actually sort actions within each group by their individual due dates. If you want to sort actions within a group, you'll need to set the sorting order as well. (You can do this by clicking on the sorting popup in the view bar, or by selecting "Sorting->Due" from the View menu.)

Does that help?

[QUOTE=Ken Case;33287]By default, the "Due" perspective groups actions by their due date but doesn't actually sort actions within each group by their individual due dates. If you want to sort actions within a group, you'll need to set the sorting order as well. (You can do this by clicking on the sorting popup in the view bar, or by selecting "Sorting->Due" from the View menu.)

Does that help?[/QUOTE]

Yep, that did it.

[QUOTE=Toadling;33286]A lot.[/QUOTE]


I really really don't have time to respond to every one of your points. Some of them are valid questions so I'm not trying to just dodge but some of them are you reading something into what I wrote that is not what I intended and I don't have time to rehash and rehash these in some sort of infinite loop.

I will answer a couple of quick points:

1) By deploy I meant to deploy to the production environment. I developed web applications for Fortune 100 companies so that is where the term deploy comes in, deploy to a production web server.
2) Critical bugs (i.e. those that affected how the application worked and did not have a workaround) were fixed, tested, and the new code deployed ahead of other planned releases. The code for these fixes was then incorporated into the other lines.
3) Of course you can't delay forever but as a private company the ultimate decision lies with OmniGroup as to when they announce and eventually release a product. NOTHING forces a release. In fact, a company can pull a product completely if they run into a significant problem. They will take a hit for that too but that is another story.
4) This isn't about shipping bug-free software. It is about how quickly bugs are fixed once you know they are there.
5) Jet Brains is a great company with great products. Unless you have done large scale Java development you probably wouldn't have heard of them.

Back to work.

Yeah, I've already spent too much time in this thread too. And I don't want any hard feelings over this really very minor topic. So please, take no offense at any of my comments.

To wrap up:

1) I still believe Omni Group's release schedule is perfectly acceptable. I am aware of no critical bugs, or even major ones, so accumulating a variety of fixes into a series of point releases seems reasonable to me.

2) True, at the most basic level, nothing forces a release from the Omni Group except the desire for the Omni Group to remain solvent. But isn't this the case for all commercial enterprises? Nothing forces Apple to release new products, but if they didn't or were very slow to market, they'd certainly lose money! So at some point, you'd better get something out the door, even if it's not perfect.

3) All my development experience has been in C++, Python, PHP, and JavaScript, so that explains why I haven't come across Jet Brains. But if I ever get into Java development, I'll be sure to check them out. Thanks for the heads up.

I haven't read this whole thread, but I have to say that the number of bugs I've encountered in 1.0 has surprised me, and that "1.0" feels more like a beta release to me. Here are some of the things I have encountered (and reported). I'm not sure which have been fixed.

1. The "Show in Planning Mode" contextual menu regularly says "Show in Context Mode" even in context mode. Also, this menu item is sometimes grayed out when it shouldn't be.

2. Repeating actions don't correctly inherit the start time when repeat from "completion date" is checked.

3. Sometimes my repeating actions are mysteriously duplicated. (Actually, I haven't reported this one because I haven't noticed a particular trigger.)

4. OF doesn't always color actions correctly; e.g. my items that are due today sometimes show up as black, not orange. Doing something that doesn't affect the action (adding an action to the project, for example) causes the affected action to change color, so this is definitely a bug.

Those are four off the top of my head that I still encounter in 1.0. There's at least one other, but I know from talking to the ninjas that it doesn't show up often and they're having trouble tracking it down, so I'll forgive them. Some of the above, especially the first two, seem to indicate lack of testing to me, however. But I'm spoiled by other OG programs, so maybe I have high standards.