Sebastiaan van Stijn's dashboard

Thanks!

Ah, great!

Do you already have an estimate on the release date for 1.8? – Sebastiaan van Stijn, on May 05, 2009 15:13

Very pleased to hear that SVN integration is here. Will discuss it with my colleagues and give it a try :)

Ok, I just liked the idea of RSS as an alternative to e-mail notifications, as RSS messages might be less 'in-the-way' than mail-notifications.

Regarding the e-mail notifications; maybe it would be a nice feature to;
- Have per-project settings (don't/do send e-mail alerts for new issues)
- Be able to set a 'threshold' (per project) for e-mails (send e-mails for priority 'major' and higher')

I like the idea of adding RSS-feeds; A possible workaround for authentication might be to use a session-id/token in the url of the RSS-feed. I don't think this will be less secure than sending authentication and/or session-id-headers; although it might be less convenient when the session 'expires', which will require the user to re-subscribe to a new feed).

(So; the user logs in. A unique url is generated for the RSS feed, which can be added his RSS-reader; This URL will stay valid for 2 weeks (for example), after which a new url will be generated).

On the other hand (authentication); if enough RSS-readers are available that -do- support authentication; It might be just a 'requirement' for this option to use ('if you want to use Fixx RSS feeds, you will need a RSS Reader that supports authentication, like ..., ..., ...')

Currently, if I'm not mistaken (will have to look into this), a user can be assigned as project-owner/manager. However, project-owners/managers don't have all the options that an admin-user has.

Would it be possible (and maybe technically easier to implement) to give project-owners all options that an admin-user has, but limited to the project(s) he/she owns?

That way, the 'admin' user can assign users to a project and those users can modify the project (adding versions/milestones etc) without having to switch to an admin-account.

Ehm.. yup.. turned out to be quite a few lines.. LOL

So here I go:
1) Will have a look at including my own stylesheet. Technically, this won't be a problem, but I always try to prevent 'hacking' the system to prevent issues with updates.

2) It's not a big issue, but I noticed it and thought I should mention it :)

4 .. 6) Again, no problem at all. Being able to add/customize colors is more of a 'nice' extra, not a big issue, I only hope that my ideas might assist in improving Fixx even further. (Although.. colors for 'priority' -will- make things more clearer at-a-glance :))

Thanks again for taking the time to have a look at my comments. Much appreciated.

Another one on my own list :) and I was thinking in the same direction; A 'lengthy' idea on this:


1) Allow uploading a custom stylesheet, which is loaded -after- the default stylesheet.

This allows for easy overriding the default styles. Maybe even add the option to upload a stylesheet -per project- to customize the look and feel for a specific project/customer (although this might be taking it a bit too far...)


2) Add a class for each priority.


I had a quick look into the HTML source and saw that currently the priority-column has two classes assigned; 'Priority' and 'darker'. My comments on this:

Keep 'style' separate from 'content'; 'darker' suggests that the color should be darker. Even though this might be the case in the current layout, it might not be in a future/custom skin (The same applies for example for html 'strong' tags, which are prefered over 'b' tags). For example, also use 'odd/even' for this.

Then add a class for each priority, for example:

<td class="priority odd priority_1">minor</td>
<td class="priority odd priority_2">major</td>
<td class="priority odd priority_3">...</td>



3) Add the description for priorities as 'title'

Currently, I don't see the description of priorities return anywhere? This might be one location to have it find it's way to the user;

<td class="priority odd priority_1" title="A minor issue">minor</td>
<td class="priority odd priority_2" title="A major issue">major</td>
<td class="priority odd priority_3" title="...">...</td>



4) Add a 'span' or 'div' for further customization


This allows me to (for example) add a background-image to replace the text, and hide the text itself using CSS; Furthermore,
this separates the 'column' style (odd/even) from the style of the column-content (priority priority1):

<td class="odd">[span class='priority priority_1' title='A minor issue']minor[/span]</td>
<td class="odd">[span class='priority priority_2' title='A major issue']major[/span]</td>
<td class="odd">[span class='priority priority_3' title='...']...[/span]</td>

(put in some '[' because my html-tags were stripped.. )


5) The same for 'Assigned User'. Add an extra class (preferably to the 'tr' tag) if 'I' am the assigned user

This way, it's -possible- to highlight rows that are assigned to me :)


6) The same for 'Issue Types' (and, when added to the issue-list: 'Resolutions' and 'Area')

This is a bit of a challenge, because these types are not globally defined, but per-project.

Possible solution for this;

- Add project-id as a 'class' (class='odd project_12') or 'id' (id='project_12.issue_23') to each row
- Add the id of the area/resolution/issue-type to the column or 'span' inside the column


<tr class="even project_23"><td class="odd">[span class='IssueType issuetype_12' title='Optimization (performance etc.)']Optimization[/span]</td></tr>


Because of the per-project definition of these properties, this might be less suitable for styling in a stylesheet. For these it -would- be best to define a style per type and store that in the database. Maybe have limited list of styles (style_1, style_2 ...) to be assigned to these properties; the combination of the
type of column (area/issueType/resolution) and the selected 'style'(style_1, style_2 ...) could then be used for styling. Assisted by the project-id in the tr-tag, this even allows styling per-project;


<tr class="even project_23"><td class="odd">[span class='IssueType style_1' title='Optimization (performance etc.)']Optimization[/span]</td></tr>


CSS:


tr.project_23 .IssueType .style_1 { color: #f00 }
tr.project_23 .IssueType .style_2 { color: #0f0 }
tr.project_23 .Resolution .style_1 { color: #300 }
tr.project_23 .Resolution .style_2 { color: #030 }

tr.project_24 .IssueType .style_1 { color: #0ff }

etc...


While implementing this, will it be possible to add an backup/export option prior to deleting a project? For example as 'SQL' dump or XML (just an idea that comes in mind when reading this issue) This way it's possible to backup/archive all project-data before actually deleting it from the system.

Not a big issue.. just an idea

Excellent! Much appreciated! – Sebastiaan van Stijn, on April 21, 2009 11:40

I will have a look at future updates of fixx. Thanks in advance

(Sorry for the large amount of comments I'm adding today, we just started implementing Fixx and I'm currently comparing my own notes with the notes posted here by other users) – Sebastiaan van Stijn, on April 21, 2009 11:38

Would it be possible to add a link to each version that links to the issues page and automatically filters the issues on the 'version' and status ('closed'). Like this:

8 of 16 issues are open [view closed issues]

or

8 of 16 issues are open [view all issues]

Ah, I also overlooked this option!

Maybe change the title for the filter to something like 'project (properties)' in stead of just 'project' to make this clear. (won't be an issue once everyone is aware of this option, but might be for new users)

Clear.

I just though it was a bit 'inconsistent', because all other columns -are- sortable. No worries; filtering does the job :) – Sebastiaan van Stijn, on April 21, 2009 10:49