ChiliProject is not maintained anymore. Please be advised that there will be no more updates.
We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.
History elements overlays revisions in Issues (Bug #807)
| Status: | Closed | Start date: | 2011-12-28 |
|---|---|---|---|
| Priority: | Normal | Due date: | |
| Assignee: | Holger Just |
% Done: | 0% |
| Category: | User interface | ||
| Target version: | 3.0.0 | ||
| Remote issue URL: | Affected version: | 3.0.0 |
Description
In the issues#show, the journal entries overlay the associated revisions which makes it impossible to click on links there.
This is because of the position:relative on some elements there which is used to position the gravatar. Unfortunately, this pulls it out of the float order somehow.
A solution is to get rid of the position:relative and position the gravatar using floats. I still need to dig a bit more here.
Associated revisions
git-svn-id: http://redmine.rubyforge.org/svn/trunk@1216 e93f8b46-1217-0410-a6f0-8f06a7374b81
[#807] Move gravatar into the journal div
[#807] Re-add details class to maintain backwarts-compatible lasses
History
Updated by Eric Davis at 2011-12-29 05:58 pm
What do you think about putting the revisions somewhere else instead of on a fake column? I'm thinking up with the Subtasks and Related Issues sections, listing each revision along with more details about them.
- Category changed from Journals / History to User interface
Updated by Holger Just at 2011-12-29 06:46 pm
What would actually be the coolest would be if the revisions were displayed interleaved with the other journal entries (sorted by time), maybe with a slightly different formatting or an icon or something.
If then there was a simple way to filter the displayed journal entries by type (could be "normal" and "revisions" for now, but could be expanded to, say, changed columns or users, or ...) it could be really useful to follow the track of the issue. Esp. if it's a longer one where several attempts to fix are required. It would also make the workflow of updating issues via commit log much clearer.
Updated by Eric Davis at 2011-12-29 07:46 pm
Holger Just wrote:
What would actually be the coolest would be if the revisions were displayed interleaved with the other journal entries (sorted by time), maybe with a slightly different formatting or an icon or something.
If then there was a simple way to filter the displayed journal entries by type (could be "normal" and "revisions" for now, but could be expanded to, say, changed columns or users, or ...) it could be really useful to follow the track of the issue. Esp. if it's a longer one where several attempts to fix are required. It would also make the workflow of updating issues via commit log much clearer.
The only problem with that is you'd have to scan the entire history to look for revisions, which would make it easy to miss one. Perhaps...
- Have the list of revisions on top like the related issues
- Have each revision inline in the history like you mentioned
- On each revision on the top, anchor link to the revision in the history (e.g. click commit X -> jumps down to journal 42)
Might be overkill for this issue though (design bug).
Updated by Holger Just at 2012-01-17 06:44 pm
I have fixed the journal markup and stylesheets so that the existing layout still works.
The idea of changing how to display the revisions is out-of-scope for this issue. So I extracted it into #837.
- Target version set to 3.0.0
- Assignee set to Holger Just
- Status changed from Open to Closed