Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
izipuho opened this issue Jan 15, 2021 · 3 comments
Open
Assignees
Labels
enhancement New feature or request

Comments

@izipuho
Copy link

izipuho commented Jan 15, 2021

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
Copy link
Owner

edtro commented Jan 16, 2021

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

@edtro edtro added bug Something isn't working enhancement New feature or request wontfix This will not be worked on labels Jan 16, 2021
@izipuho
Copy link
Author

izipuho commented Jan 17, 2021

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 edtro removed the wontfix This will not be worked on label Jan 17, 2021
@edtro edtro self-assigned this Jan 17, 2021
@edtro
Copy link
Owner

edtro commented Jan 17, 2021

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

@edtro edtro added In Progress and removed In Progress bug Something isn't working labels Feb 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants