search

edtro / EdTro.AzureDevOps.Extensions.querybasedboards

Query Based Boards enables a user to visualize the result of work item queries as a board and track the dependencies.
MIT License
23 stars 2 forks source link

BUG. Custom additional fields on WI card. Board crashes on some fields. #37

Open izipuho opened 3 years ago

izipuho commented 3 years ago

Hi! I think it's better to discuss here, rather then at VS Marketplace. As I published as VSM I tried to add custom field from another extension (our own development):

{ "fields":[ { "name":"Logrocon.PerformerIT", "title":"Developer" } ] }

it has same type as AssignedTo. And it crashed the board: Empty board

But when I add string field from same extension:

{ "fields":[ { "name":"Logrocon.CustomerContact.1C", "title":"Contact" } ] }

everything goes normal: Normal board

edtro commented 3 years ago

Hi @izipuho

Unfortunately not all types of fields are supported. These types requires more styling... so I will have to implement those types at some point (but I do not know when). But I have documented this limitation in the config.md... just look at the last sections (completely at the bottom of the document)

It is strange however that the board is crashing. The same behaviour occurs when you are using a field that does not exist. So this could be seen as a bug. I will have to look into this. But I think we know the origin of the problem (adding the 'System.AssignedTo' wont help as a test, because I am filtering this field, because it is already added to the board).

Kr Edward

izipuho commented 3 years ago

Oh! That's what you mean by Identity field! Sorry. :-) I'll try to find another Identity field at my project to test. On the second screenshot you can see Contact as text field. It also contains a name. It's pretty ugly but it still works. Maybe you can treat Identity as text at first?

edtro commented 3 years ago

I am implementing extra styling for the field 'System.Project' (and some extra filtering options regarding this field... because I am working at a customer that is really using the multi-level setup of epic/feature/story). So it would not be that hard to include this type of field. So stay tuned.

Unfortunately I cannot give any timetables... it is sometimes very hard to find some spare time.

Kr Edward