tracker
tracker copied to clipboard
crs-tools
CRS Ticket Tracker
Nur eine kleine Idee die mir auf dem Easterhegg gekommen ist: Um Project properties im Block einfacher bearbeiten zu können wäre es ggf. sinnvoll auf eine große Textbox umschalten zu...
*Issue migrated from trac ticket # 141* **component:** unknown | **priority:** major #### 2017-04-16 15:35:19: @MaZderMind created the issue ___ See [TODO](https://repository.fem.tu-ilmenau.de/trac/c3tt/browser/Application/Controller/Import.php#L300). Currently fails with database exception
To minimize issues with duplicated projects and simplify project creation, default sets of project properties could be introduced. A set would hold multiple properties, some of which might be marked...
This information is useful in the releasing process, where the links can be rendered into the description for example.
*Issue migrated from trac ticket # 140* **component:** unknown | **priority:** major #### 2017-04-16 15:30:52: derpeter created the issue ___ There are some intermediate states with errant behaviour. See attached...
As follow up to #185 and in context of https://media.ccc.de/v/geekend2018-5-graphql – what is your opinion on adding a GraphQL API to the tracker? It looks like there exist the corresponding...
If the ticket creation transaction is aborted the import is not finished and is left in a sort of failed state, without a warning for the user.
When debugging setups, it would be nice to have a dedicated "retry" button which removes the "failed" flag an resets the state to the previous one. Mockup: 
Just a quick note: When manually changing the state e.g. a recording ticket from `recording` (encoder X) to `recorded` the UI could ask the user if the assignee should be...