Daniel Woste

Thanks for the report and good finding :+1: I think a fix should be easily possible by checking the keys for duplicates during the build.

@twodrops: A later check is in my understanding not possible, as a Need with the same Id may have already overwritten the original one during the merge. So there will...

Have a new idea for a solution. We can check for ID duplication also during merging the result of a worker into the "global" sphinx env. As this `merge()` is...

Thanks for reporting this bug :+1: My first guess without checking the code: We are using Sphinx-Design for the dropdown feature. But this package is not an official dependency of...

You can customize the used template by ``needreport`` via a config variable: https://sphinx-needs.readthedocs.io/en/latest/configuration.html#needs-report-template There you see also the default template and your own template can base on it.

Thanks for the patch 👍 Can you create a PR for this, so that our CI can already test it? We may need the id for some JS actions. I...

@iSOLveIT do you see some problems with the Collapse-solution from yesterday if the HTML output is changed like this?

I'm not sure if I like this much, as the table is the need element and it should have the related need ID. Technically it is no problem to get...

To be honest, I'm not sure what the expected behavior is. My personal opinion was, if you use a filter-string, you don't use the other mechanisms anymore. I didn't even...

Maybe interested in a merge? ([Twitter post](https://twitter.com/DanWos/status/1600480177087254528)) The awesomesphinx list could be part of your docs (some kind of a subpage) and single elements get selected to be presented your...