|
Ideally, each column should be configurable as either being a text value, drop list etc.
The edit screen could look like this MARKET | Cost (USD) | Activated (yes/no) | ... The MarketX labels should be fixed, i.e. the user needs to input info for X nr of markets. An alternative could be that the "Labels" (Market nr in this example) is chosen from a drop-list. And after inputting one "row" the user can choose to add another "row" (market in this example) Hope you get the picture? > Hope you get the picture?
Yes, sounds interesting. I'm wondering if it would be better thought of/implemented as a special layout (sublayout?) of regular custom fields, rather than as a completely new custom field type. At some stage it will be possible to use Wiki-like syntax to create tables, so one could visually achieve the same result with a normal textarea field. Wiki markup is likely to happen sooner than this, so do you think it would meet the immediate need? Yeah, maybe it's smarter to do some special layout of the current fields.. as a user I don't really care how it's implemented
I don't know how wiki-markup works.. it sounds like I still have to create tons of separate fields though and then use wiki-markup to improve the layout? Since I already have a zillion custom fields and JIRA currently does not have good support to organize them this does not sound like a great solution... i.e. it won't meet the immediate need Re. Wiki markup, the way it works is you enter text, almost exactly as you did in the description:
And this gets rendered into a proper HTML table. This is presumably fine for displaying tabular information, but no good for entering structured info when creating issues. I'll leave this issue open for now to gain votes, and it will come up in future planning meetings for consideration. Cheers, You probably have to do this by using JAVA-applet :|
Our need is to create manual test cases like this: Text Field: Test case name <b>The table:</b> Steps .. but if it is possible to do it by using HTML... it would be great. -JP Hi JP,
The wiki formatting renders HTML when the issue is displayes. Does this meet your needs? Thanks, We have a need to add a list of file names to a request in jira. We currently need to attach an excel spreadsheet to the request. This of course is prone to error.
Hi, I need this necessary feature? When you plan to implement this custom field?
Releted link: https://support.atlassian.com/browse/JSP-27524 Hi, guys
This is Luke from Korean partner, Goldpitcher. I think this function is essential if the data needs to be searched by column and reported with it. In this case, my story is like at first stage user add custom field, option table size and label (comma separated) can be set. My question is that I wonder this kind of story is possible for implementing with plugin. Any advice will be helpful. Cheers, As custom fields can be implemented as plugins it should be possible to write this as a custom field.
However, you can save yourself a lot of trouble by using wiki markup as pointed out by Jeff: For more information on using wiki markup, please see: Cheers, Anton, decision like this
"However, you can save yourself a lot of trouble by using wiki markup as pointed out by Jeff: http://jira.atlassian.com/browse/JRA-6696?focusedCommentId=35992&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_35992  "is usefull. But my users of system need to get more simple interface - without wiki markup, only field where they can input only value of this field. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
New Feature
Open
Major
Table - new custom field type
How will this custom field work? ie on the edit screen what do you expect to see? Text boxes for each value? Or just a TextArea that lets you put in the HTML for the entire table?