Dominik Klein
Dominik Klein
Yes, again a difficult question and I think there are different expectations in the usage. I was only wondering, but now I'm also not sure what's the best.
Sounds for me also like the best solution.
Yes i think it's a complex topic to make this work in the best way. For example you added now the aria-describedby for the "help" text, but if a error...
Yes, this looks good from my side.
We want to handle it with the following solution: - Add multiple article type variables (e.g. last_article, last_internal_article, last_customer_article, ..., needs to be defined). - A migration for the current...
@bolah2009 we defined the following possible variables: `last_article` (equal the current `article` usage), `last_internal_article`, `last_external_article`, `created_article`, `created_internal_article`, `created_external_article`
I think it's not completely related to this bug. Currently, I have also a problem in that my watcher on the result is triggered twice when I use the `refetch`....
@Stubenhocker1399 Thanks for the report. In general, it's correct that the merge handling is currently not in the "best shape". But in the end, we are not only talking about...
@Stubenhocker1399 Looks to me like a bug, because of its inconsistent state after the ticket merge action. Maybe you can create an issue with this behaviour?
@Stubenhocker1399 Thanks for your effort :-) Like described in the related issue is this a more complex topic and at the moment we want not only to merge this small...