Is there a possibility to visually represent data in a scrum board format.
Everyone is familiar with the Trello / Jira / Scrum board and I’d like to display the progress of certain entities in such a setup.
I have been able to get the closest by creating a view that fills the column accordingly, and therefore maintains the connection to the underlying entity (defined by the row).
Additionally, I have attempted to display them in a Cube / PivotGrid. This leads to the same ‘empty row’ result.
Is there another component or method to construct such a scrum board view?
Thanks for your suggestion. If it can visually look like this that would be the ultimate solution.
The dragging/dropping of items, or moving of the phases will happen in the background due to other ongoing processes. The goal is to just visually represent them this way.
Do you have suggestions on how to implement the visual aspect of this, without dragging/dropping, in Universal GUI?
You could create a view with something like this:
SELECT MAX(CASE WHEN phase = 'Design' THEN value END) AS Design, MAX(CASE WHEN phase = 'Implementation' THEN value END) AS Implementation, MAX(CASE WHEN phase = 'Testing' THEN value END) AS Testing FROM ( SELECT phase, value, ROW_NUMBER() OVER (PARTITION BY phase ORDER BY value) AS rn FROM #phase_table ) src GROUP BY rn ORDER BY rn;
Resulting in:
Drag and drop would be nice to have though, I imagine. In that case I would just create a screentype with vertical grids side by side.
@jkruter thankyou.
It results in this table, which is desired.
When visualizing, I would lose the reference to the record that would decide which detail view to show.
Executing tasks/showing detail information is to my knowledge not possible in this manner.
Additionally, you mention a screentype with multiple vertical grids side by side. How would I go about filtering the grids individually, since I must define the screentype on a subject, all grids take the data, but also the filters etc. from this selected subject. Do you have ideas for this?
@Stijn Schuurman Looks good to me (once I copied it and pasted it into a bigger editor):
Not the intended result?
@jkruter
Sorry! I had pressed `Send` too early, and was not yet done writing the rest of the text. Please read the comment above your comment again now that it is updated.
Ah I was too quick to reply.
But yes, I don’t think tasks can be linked to individual cells, only to rows as far as I know. And with the above solution you lose the link to those values.
The way I have combined multiple tables/views on one page that have no real relation with eachother (no common key), is just by joining them on 1=1. So you create a separate view for each phase, and pick one to be the “parent”, which has a reference to each other view, so it can display them as “children”/detail screens.
You could also create a new table/view, which can serve as the parent for all the phase views. In my case I also used this to display some statistics at the top, like amount of items total, % done, etc..
I haven’t done it in a while, but it should be possible
@jkruter
Alright! Sounds like a way to combine multiple grids to get the “flow” from side to side, while being able to select individual records in this views.
Do you happen to recall how to setup the “children”/detail screens, so that they do not become tabbed, but immediately visible on the mainscreen view?
Actually now that I think about it, you should definitely create a parent table/view and attach the views you actually want to display to that. If you do it the other way, the detail views will reload every time you make a different selection in the “parent” view.
Here is an example:
The top-left view (sales_order_palletbuilder_info) is a view that has no relation at all to stock_location. I’ve created a reference between the two (sales_order_palletbuilder_info to stock_location) with no source and target columns.
This allows me to select it in the subject links for sales_order_palletbuilder_info:
Which would put the full “stock_location” table in the screentype, without any filters or real links to the parent table. So Imagine your columns are each like stock location, and you create a parent view called “trello_overview” or something, connect it without source and target columns, and it should work.
In my case the other tables do have source and target columns, but they don’t have to.
For screentype you probably want something like this:
Define the screenarea for each, you can add more than just A and B under the screen areas tab. Also set show borders and show tab header to false, and setup a screentype without the action bar and everything for each view (otherwise there will be a lot of clutter).
Hopefully you only need one task, then you can use double-click, otherwise you’d need an action bar on each grid.
Do keep in mind that the more tables there are on the page the slower it seems to load. This is something I’m still trying to improve myself (not much I can do about it though, I’m afraid).
The actual parent, if empty, should disappear. Mine isn’t empty though so it might cause issues I’m not aware of if it is an actual empty table
I have adopted your recommendations @jkruter, this starts to look really good.
Will apply a table task to the views so that it can execute some action.
So far, I was not yet able to remove the component on the left. I used a new view with a single column, which is returning an empty table. However, the form is still visible at all times. Do you have some more suggestions here?
I must add that the form eventually disappears when the data has been loaded and the data is empty.
@Stijn Schuurman You should be able to hide the form field, under subjects > components > form, setting form type to hidden. Might also be able to have a view without any columns, but I’m not sure about that.
You might also want tab headers on, so that you can see the phase/view names above your columns.
@jkruter
Absolutely, sweet!! Was experimenting with the tab headers, and that allowed me to translate the view names to the desired phases. Nonetheless, thankyou for the suggestion.