Martijn Laarman's dashboard

Martijn Laarman replied on February 17, 2009 14:19 to the idea "RTF descriptions ?" in hedgehog lab:

Cool! i had no idea textile was enabled. Although lists and headers i can't seem to get right. Something like the wmd-editor with previews and an enable RTF post button would all help a great deal :)

Martijn Laarman shared an idea in hedgehog lab on February 17, 2009 13:45:

RTF descriptions ?

Is it possible for future releases to support some sort of RTF descriptions. By allowing certain html, UBBCode (better) or even Markdown which i never really liked untill i actually used it on stackoverflow (which im sure you as self proclaimed Joel Spolsky fan boys have worked with as well :))

Martijn Laarman shared an idea in hedgehog lab on February 17, 2009 13:11:

DashBoard and closing issues.

If i close/resolve an issue with a comment in the dashboard it comes up as 2 or 3 different actions (Closed/Resolved and Comments depending if i Close or not). Any particular reason for this ? It would be nice if they were condensed into one or atleast don't show the Comment Action as now i see the comment twice but with different lengths :p

It seems the Close action allows for longer text's on the dashboard then comments which are cut of sooner.

Martijn Laarman replied on February 13, 2009 09:30 to the question "When does fixx send out email notifications ?" in hedgehog lab:

Ahh after a couple of minutes it did sent me an email saying a new comment had been posted. It also sent me an email of resolving the issue under a different user.

As the homepage states

Our email integration goes one better than traditional bug tracking systems, as it is geared towards preventing notification spam and is geared towards human interaction, leaving you in control.

Is this delay because it queue actions and sent them off with a delay so people only recieve 1 email ? So if a user resolves and 1 minute later unresolves the resolve action is pushed of the queue ?

I'd like to know more what the prevention of notification spam entails and which actions trigger an email.

Martijn Laarman asked a question in hedgehog lab on February 13, 2009 09:25:

When does fixx send out email notifications ?

Hey i've set up an SMTP server and configured it in Fixx. The test email is sent with no problems. However i put myself as watch on a certain issue and edited it/resolved it. Of both actions i didnt recieve an email. So i tried logging in as another user and edited/unresolved it and commented on the issue. Of all actions i didn't get a notification.

Is there somethng i am doing wrong ?

Martijn Laarman reported a problem in hedgehog lab on February 12, 2009 15:48:

Archived projects

Several actions on an archived project just give back a black screen such as adding a new Issue Type, Area, Resolution and version.

If a message could appear why the screen is blank it be great.

Martijn Laarman shared an idea in hedgehog lab on February 12, 2009 15:37:

Remember last project i wrote time on.

Quite often i have to fill in numerous issues in one go for a project, say from taking notes on pen and paper at a customers location. In these case i "create issue" 10 times in a row and it would be really handy if Fixx remembers that i wrote my last issue on ProjectX so theres a good chance this one is about ProjectX as well.

Another thing i noticed is that if i select the wrong project unknowingly and fill out the rest of the comboboxes alot of them are reset if i change the Project. I get that different projects have different users and issue types but if the one I selected before the project change is still available in the newly selected project it would be nice if Fixx was smart enough to keep them instead of resetting them,

Martijn Laarman replied on February 11, 2009 23:26 to the idea "Next and previous buttons on issue detail view." in hedgehog lab:

excellent stuff! i can't wait for 1.8 really keen on finding out the version control stuff you guys have planned :) I started on trying to build an eclipse addon for listing open bugs as a pet project at home to keep up with my Java but if this is something in the pipeline i'll wait patiently whats in store :)

Martijn Laarman shared an idea in hedgehog lab on February 11, 2009 11:33:

Next and previous buttons on issue detail view.

Gmail has a really cool future (perhaps it's still one of their lab futures) that allows you to open a mail and by holding the left mouse button and going left or right go to the next and previous email. Going up will go back to the inbox.



The real nifty part is that when i do a search in gmail and i open up an e-mail these mouse gestures now move back and forth within my search as suppose to my inbox.

Whilst the mouse gestures might be a bit time consuming to add something similar i think can be added easily within Fixx.



These next and back buttons remember the filter i came from and brose through that. Save going back to issues figuring out where i came from and pick the next (or previous).

Martijn Laarman reported a problem in hedgehog lab on February 11, 2009 10:26:

Requiring Time logging bug

I have require time logging enabled for a project and when i want to resolve an issue it will give me a message saying I need to log time just nicely. However if i leave it untouched it wont prefent me from resolving the issue instead it gives this error message:

fixx could not log your time as the data provided was in an invalid format. Please ensure you have provided the date in the right format and entered the time in decimal number format.

The issue however is still marked as resolved (Fixed).

Martijn Laarman reported a problem in hedgehog lab on February 11, 2009 09:36:

Permalinks

I'd love to be able to send out links such as:

http://<myfixxdomain>/issues/33

Right now this transfers to the login screen but after logging in it doesn't transfer the client back to http://<myfixxdomain>/issues/33

</myfixxdomain></myfixxdomain>

Martijn Laarman replied on February 10, 2009 19:13 to the question "How can a client see all the issues ?" in hedgehog lab:

Having an "All issues" filter by default would already be a HUGE addition in the way we (plan to) use fixx definitely! Also for our clients Fixx will be a lot easier to grasp up front!

One remark: creating a new filter always seems to append "open issues" as one of the criteria whilst the default view may not change in the future to "All Issues" will this appending behavior be up for review ?

Martijn Laarman replied on February 10, 2009 17:35 to the question "How can a client see all the issues ?" in hedgehog lab:

It seems that Open really means anything not 'Closed'.

And that Status is Open or any of the resolution items.

Perhaps this is due to the fact that english is not my native tongue but the use of "Open" really seems to miss context from my perspective.
If you say listing all "Open" projects i dont really expect resolved issues to be there as listing open includes resolved but not closed but listing resolved does include Closed.

So you have Open = anything not closed
Resolved = anything not Open.

And resolved falls in between both this seems very ambigious to me :/

I still feel that an ALL filter is missing with that also shows the status "Closed"

Withouth the afformentioned assumption alot of this ambiguity would fade away.

Martijn Laarman shared an idea in hedgehog lab on February 10, 2009 17:18:

"Create new issue" button more vibrant

Something i noticed when getting my colleagues up to speed on Fixx is that the "Create New Issue" button is not visually apparent enough. They spent a conciderable time (1 minute) looking for it followed by a big "AHHH THERE IT IS!" moment.

Martijn Laarman replied on February 10, 2009 16:35 to the question "How can a client see all the issues ?" in hedgehog lab:

To clarify my position a bit more.

If clicking on the issues tab would get you ALL the issues by default it would really kill alot of ambiguity in the current user design.

Clicking issues gives me all the issues (which is what anyone would expect from clicking issues) clicking an excisting filter or creating a new one filters the result set to a subset which again seems very logical.

Right now it's assumed that if someone clicks issues they only want to see the open issues which i find a very big assumption. Of all my 10 colleagues that are using Fix now NONE expected to see only the open ones.

The fact that issues remembers my last filter however (what Fixx does) i find a very good feature of Fixx but removing the filter should not fall back to all open issues but all issues.

Right now if i create a new filter purely based on 1 criteria (namely Project == ProjectX) the filter that is applied is the following:

Filtered by open issues in project(s) ProjectX. Sorted by descending Priority.

I never told it to filter only open issues i just wanted to see ALL the issues off ProjectX.

This is one of the biggest useability nuisence i have with Fixx: the assumption i only want to see open issues.

In short: assume i want to see all issues unless my filter states i only want to see open issues.

Martijn Laarman asked a question in hedgehog lab on February 10, 2009 16:20:

How can a client see all the issues ?

Hey guys,

How can a client see all the issues when i click (issues) all i see are:
- All open issues
- All assigned to me
- Watching

Issues that i close as User won't show up and i can't see how i can bring them back into view logging in as client.

A default filter of (All issues) would be a very nice addition.

I much rather see that clicking on Issues shows me all the issues (paginated) irregardless of their status and that applying a filter limits the result set. This seems alot more logical to both me as User and my clients that only login from time to time to check on progress or to report new issues.

Right now Clients have the feeling that issues that I have resolved are deleted and fill them in again.

Martijn Laarman replied on February 04, 2009 12:32 to the idea ""All open issues" missing project and area column" in hedgehog lab:

In your blog post you mention the hover popup to show additional meta data. This however prevents you from scan reading the open issues page quickly.

I really feel Project and area are important enough to make a quick read decision where as due date and created date is something we as humans (or atleast I) cannot quick scan read and are fine to put away in a popup, in fact i much prefer them in the popup so they don't clutter my quick scan reading. Like a huge list of 20digit numbers requires your focus to keep track of position whereas a sorted string of say 25 characters does not.

Martijn Laarman shared an idea in hedgehog lab on February 04, 2009 11:43:

DashBoard doesn't show newly created issues just activity within the existing issues.

I'm a fanatic F5'er and would really like the dashboard to also include notices of newly created issues. Instead of just the activity within issues.

Right now i have to keep switching between the dashboard and issues tab to get a good overview of anything i might have missed since the last time i pressed f5 (usually 5 minutes ago :))

Martijn Laarman shared an idea in hedgehog lab on February 04, 2009 11:39:

"All open issues" missing project and area column

I really miss these 2 columns to give the title of the issue a bit more context.

Martijn Laarman shared an idea in hedgehog lab on February 04, 2009 11:31:

Making private area's

We follow a pretty strict DTAP idiom (development, test, acceptance production environments) and we'll often make test releases for inhouse testing, Ideally we'd like to create a private area (users only) that we can use internally to report bugs whilst having the other area's be representative for what our clients test/experience bugs on (acceptance and production).

Also this way we can set up start up area's that haven't been enrolled to the customer yet without clutering the clients perspective on his project.