Damian Nicholson's dashboard

Me also - this only occured after updating to 1.1.1, have completely uninstalled Little Snitch to which was to no avail – Damian Nicholson, on May 05, 2009 22:53

As agreed we've just implemented the second point on your list here Sebastiaan - adding a class to each of the priority cells of the issues table, so you should be able to style this anyway you want as of 1.8 onwards :) – Damian Nicholson, on May 05, 2009 14:57

Hi Wilhelm,

Yes I can see how this is confusing as open means different things based on the context it's in.

Your very right about the filters issue. In order to differentiate between the two this is something we've planned to address - when creating a filter for all open issues it should purely mean open and nothing else.

Hi Sebastiaan,

Thanks for making this clear to us. We're working on giving the styling of fixx an overhaul in a future release.

Hi Bon,

Indeed you can link issues to others using the following shortcode.

issue@23

Where 23 is the issue id of that you want to link to. This will display as a hyperlink which will take you to the linked issue.

We do like the idea of using #23 however this conflicts with the text parser we currently use. Hope this helps :)

Hi Arthur,

Apologies if our installation instructions don't point this out clearly, this is a fault on our part and will make sure we update them accordingly. Thanks for pointing this out to us :)

bin is a folder within fixx, so if I were to download an unzip a fresh copy, I would be presented with fixx-standalone-1.7 folder, which I can navigate to in Finder.



It's in this folder that you can find the bin file we were referring to. bin is basically a directory where we hold a number of scripts, the most important of which are startup.sh and shutdown.sh, which as you can guess can be run to start and stop fixx. In order for these scripts to work their magic, they have to be made executable. The chmod command does precisely this. Don't worry though, as you only have to do this once.



Since we want to make a bunch of files executable its both quicker and easier at the command line using the Terminal app, so we suggest you do it this way.

If you downloaded and unpacked your fresh copy of fixx to your Desktop, open Terminal app, and type the following. This is essentially what we done before in Finder - navigate into fixx, into the bin folder.

cd Desktop/fixx-standalone-1.7/bin/



Obviously if you downloaded it to your Downloads folder, or Documents you need to change the location of the first directory. Since you are now in the directory where the scripts(.sh files) are which we need to make executable, we can type the chmod command you were asking about:

chmod +x *.sh

And that's it, you can startup fixx by typing this command in Terminal.

Note: You have to be in the bin directory to run the following commands when you startup and shutdown fixx.

./startup.sh



Similarly, to shutdown fixx you run ./shutdown.sh.

We hope this clears things up for you Arthur, obviously if you have anymore questions, don't hesitate to ask :D

Hey Martijn,

We'll take this issue onboard for a future release, as it's a very good point your making. We agree that the UI on the dashboard is in need of some improvement, so look forward to seeing some exciting changes in the near future.

All your comments so far have been very valuable to us, thanks very much! We're glad your digging fixx :)

Unfortunately, I can't commit to hinting when version 1.8 will be released, but rest assured you won't be waiting too long.

This is weird as once a user views an issue in detail, close(available as part of the Resolve action) and Delete actions should be present in the pane on the right as shown in the screenshot below.



Can you clarify that this is the problem your having? As if these actions are not appearing, then it's obviously a bug which must be fixed.

That's also correct about Clients not being able to close or delete issues. At present Clients within fixx can only create, view and comment on issues, as our research in creating fixx showed that these actions are all that a Client should need.

Your feedback is gold Martijn, loving it all! :D

Hi Martijn,

Thanks for this, we think this an excellent idea and will take this into consideration for a future release of fixx. Obviously we just have to think about workflow and how a feature like this would fit in, both from a users perspective and from an administrators, since we've tried to make fixx as flexible as possible.

Hi there,

We're very sorry to hear that this is the case, and for that we apologise sincerely.

If you can provide us with some more specifics of your installation, i.e. operating system, version of JDK, the paths you have set etc. that would give us a bit more information so we can go about troubleshooting this matter. Rest assured that we have filed this and we'll get straight on resolving this issue as soon as you are able to provide us with this info.

Obviously we appreciate you pointing this out to us, as if this is a bug we have to make sure it gets fixed as soon as possible, so that we can either release a patch or include the fix in the next release.

BUG!

Yeah this was an oversight on our part Martijn, and we apologise for this. This issue has been logged, and will be resolved in the next release of fixx. Thanks for all your feedback on here, your awesome!