Rules Hub
Code Ruleset
Rule priority, scope & exceptions
Use this to align rules with the senior-level structure (P0/P1/P2, scope, exceptions/tradeoffs).
Set repository components and the default assignee when creating Jira work
When Jira task or subtask creation is authorized, select the existing component for the actual repository and normally assign Franko. Apply these defaults to each issue explicitly and verify the saved metadata.
Bad example
| 1 | {"type":"Sub-task","summary":"Add feed ingestion","components":[],"assignee":null} |
Explanation (EN)
The subtask omits repository ownership and the configured default assignee; a parent does not guarantee either field is inherited.
Objašnjenje (HR)
Subtask nema komponentu repozitorija ni zadanog assigneeja; ne treba pretpostaviti nasljedivanje tih polja s parenta.
Good example
| 1 | {"type":"Sub-task","summary":"Add feed ingestion","components":[{"name":"service-api"}],"assignee":{"accountId":"verified-default-owner-id"},"status":"Backlog"} |
Explanation (EN)
After resolving the real component and owner in the project, explicitly set them on the issue and verify its initial status. This is a conceptual metadata example, not a Jira REST payload.
Objašnjenje (HR)
Nakon provjere stvarne komponente i vlasnika u projektu, postavi ih na issue i provjeri pocetni status. Primjer prikazuje metapodatke, nije Jira REST payload.
Notes (EN)
Activate for explicitly authorized Jira Task/Sub-task creation or requested metadata updates. Inspect the real project Components and match the verified repository or infrastructure responsibility; do not invent component names. Apply the component to each repository task and each relevant subtask, without assuming inheritance. In Franko's workflow, normally assign newly created work to Franko Solomun using a verified Jira account unless another owner is specified or the task clearly requires a different agreed owner. Keep new work in Backlog unless requested otherwise. For existing issues, preserve status, legitimate components and other metadata; reassign existing owners only within the authorized scope. Verify component, assignee and status after writing. This default does not authorize unsolicited ticket creation, historical bulk edits, Git publication or deployment.
Bilješke (HR)
Primijeni kod izricito odobrenog kreiranja Jira Taskova/Subtaskova ili trazene izmjene metapodataka. Provjeri postojece Components u projektu i odaberi komponentu stvarnog repozitorija ili infrastrukturne odgovornosti; ne izmisljaj nazive. Postavi komponentu na repo task i svaki pripadajuci subtask, bez pretpostavke nasljedivanja. U Frankovom workflowu nove taskove vecinom assignaj Franku Solomunu preko provjerenog Jira racuna, osim ako je naveden drugi vlasnik ili postoji jasan dogovor za drugog vlasnika. Novi rad ostaje u Backlogu osim ako korisnik trazi drugacije. Kod postojecih issuea sacuvaj status, relevantne komponente i ostale metapodatke; mijenjaj assigneeja samo unutar odobrenog opsega. Provjeri component, assignee i status nakon spremanja. Ovo ne daje dozvolu za samostalno kreiranje taskova, povijesne bulk izmjene, Git objavu ili deploy.
Exceptions / Tradeoffs (EN)
Explicit user choices for component, owner or status take precedence. A cross-repository parent may legitimately need multiple existing components. A project without Components may use its established taxonomy instead; if no valid mapping or owner can be established, report the gap rather than create a new component or assign an unrelated account.
Iznimke / Tradeoffi (HR)
Izricit korisnikov odabir komponente, vlasnika ili statusa ima prednost. Parent koji obuhvaca vise repozitorija moze imati vise postojecih komponenti. Projekt bez Components moze koristiti svoj postojeci nacin oznacavanja; ako nije moguce potvrditi komponentu ili vlasnika, navedi sto nedostaje umjesto kreiranja nove komponente ili odabira nepovezanog racuna.