Feature #8417

per tracker configurable issue form layout with preview

Added by Terence Mill over 6 years ago. Updated 11 months ago.

Status:NewStart date:2011-05-20
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:UI
Target version:-
Resolution:

Description

I thought about an approach to make the issue form layout completly configurable by user and i found it!

Being able to set issue form layout, would need a to configure table cell for every field.

E.g

field column row
title 1 1
subject 1 2
description 1 3
Status 1 4
Priority 1 5
Assignee 1 6
Category 1 7
Affected version 1 8
Start date 2 4
Due date 2 5
Estimated time Hours 2 6
%Done 2 7
Resolution 2 8
Files 1 9

The algo to make a table layout of this is pretty simple. It has to search for all list entries with same row number and make a table with number of columns used in this rows. In the redmines standard issue form case (see table above) first 3 rows have one column layout, row 4-8 have 2 column layout and row 9 has one column again).

A Preview Link can show how the issue form will be rendered with the entered value in the layout configuration table.

See my wireframe demo for better imagination.


Related issues

Related to Redmine - Feature #8447: support for custom fields to be structured like descripti... Closed 2011-05-26
Related to Redmine - Feature #4388: Ablitity to rearrange tracker fields for particular project New 2009-12-11
Related to Redmine - Feature #7784: Ordering/Placement of Custom Fields New 2011-03-04
Related to Redmine - Feature #12250: Configure order custom fields New
Related to Redmine - Feature #3543: Improve 'long text' custom fields Closed 2009-06-25

History

#1 Updated by Terence Mill over 6 years ago

Ups.. wrong link

Checkout demo here

#2 Updated by Terence Mill over 6 years ago

related to #8447 in terms of positioning fields.
The input type configuration shall be part of the global config, not like the issue form layout which is configurable per tracker, like described here

#8447 is a nice extension to this or the other way round.

#4 Updated by Terence Mill over 5 years ago

Dupes

  • Feature #8447 support for custom fields to be structured like description field

#5 Updated by Terence Mill about 5 years ago

Sorry, but the wireframe went offline cause tiggr decided to make its service paid, and took any content created before inside this. That is bad company, so i decided keep em go and die with it.
However the idea is so simple to imagine without wirframe too.
You just start drawing one grid per row (or optimized: and all following rows with same number of columns configured). You iterate with this aldo ascending the row count and attach every new of row x under the grid of row x+1 (or optimized: x+n rows following with same number of columns configured).
With this algo you can even allign fields flexible everyhwere, like spawn first row beyond second row, although first row only has 2 fields and second 4 row for example:

Configuration:

field row colum
field 1 1 1
field 2 1 4
field 3 2 1
field 4 2 2
field 5 2 3
field 6 2 4

..would look like Layout

field 1 field 2
field 3 field 4 field 5 field 6

You see you can span lesser num of fields.

What is needed now to be able beyond do complete left orientation of fields is some field placeholder to use fields so that yoi are completly free of field orientation.

This could look like this:

field row colum
placeholder 1 1
placeholder 1 2
field 2 1 4
field 3 2 1
field 4 2 2
field 5 2 3
field 6 2 4

..would look like Layout

field 2
field 3 field 4 field 5 field 6

So the only field in row 1 is spanned ony over the right two col 3 and 4 instead over the complete range. This is only need to fill from right to left.

#6 Updated by Jonathan East about 5 years ago

+1 for this feature. I think this would be much easier if it were just a simple drag and drop.

#7 Updated by Terence Mill about 5 years ago

Yeah, but much morw work too. I am not sure if this effort is used in the first step, if this is only configured by the admin.

#8 Updated by Terence Mill almost 5 years ago

Ping! Hopefully this issue form layout designer gets some attention.

#9 Updated by Philip Lapczynski almost 5 years ago

This would be fantastic. As a user with a lot of custom fields, this is really something that would take this to the next level. It would be great to be able to group fields in the way we want.

#10 Updated by Daniel Felix almost 5 years ago

Well, this would be great to have.
I also requested some feature which could be handled with this solution too.

+1

#11 Updated by Dipan Mehta over 4 years ago

This looks like a great generic solution.

It is a super set for many issues: #4388, #7784 and #12250.
Also, this can be related to #3543 which talks about better layout when long text fields are used.

#12 Updated by Nathanael Hansen over 4 years ago

+1 for this feature

#13 Updated by Joel SCHAAL over 4 years ago

+1 as well, can we have some feedback from the dev team about that issue ?
It has been sitting here for 2 years with no feedback (and I have not seen any on the related tasks as well), is it to be considered as a Will not fix ?

#14 Updated by RaĆ­ Kuhn over 4 years ago

+1 waiting feedback too

#15 Updated by Michelle H about 4 years ago

+1 Would love an update on this.

#16 Updated by Maxime Vez almost 4 years ago

+1 I would love this as well.

#17 Updated by Daniele Pedroni over 3 years ago

+1 also for me, Redmine core is great but it would need some appearance enhancement, IMHO.

#18 Updated by Gimhan Sumanasekera over 3 years ago

Love to see this as a feature in Redmine!

#19 Updated by Darth Vader over 3 years ago

+1

#20 Updated by Jethro Yu over 3 years ago

+1

#21 Updated by Sebastian Paluch over 1 year ago

+1

#22 Updated by Pavel Kestefran 12 months ago

+1

#23 Updated by ale dp 11 months ago

+1

Also available in: Atom PDF