{
    "summary": "Implement all the basic ticket param functionality",
    "mediaType": "text/html",
    "@context": [
        "https://www.w3.org/ns/activitystreams",
        "https://forgefed.org/ns"
    ],
    "context": "https://vervis.peers.community/decks/br6Go",
    "history": "https://vervis.peers.community/decks/br6Go/tickets/EZQOv/events",
    "published": "2019-12-28T17:11:04.678741Z",
    "dependants": "https://vervis.peers.community/decks/br6Go/tickets/EZQOv/rdeps",
    "dependencies": "https://vervis.peers.community/decks/br6Go/tickets/EZQOv/deps",
    "content": "<p>Check the following:</p>\n<ul>\n<li>Who should be able to set/unset issue labels by default, when creating issue and when editing? Who’s allowed to do that in NAB / Gitea? Issue author? Repo team? Both?</li>\n</ul>\n<p>Implement the following (or verify that it’s implemented and works):</p>\n<ul>\n<li>When editing a project, either the workflow can’t be changed, or a workflow change involves a check whether any tickets use the current workflow <strong>(workflow can’t be changed)</strong></li>\n<li>When editing/deleting a workflow field, it checks whether any tickets use that field or the values being changed/deleted <strong>(field, enum and ctor deletion and editing not implemented)</strong></li>\n<li>Ticket params can only be set according to roles; add a role operation for this if needed <strong>(ticket creation doesn’t allow to set params; ticket editing allowed only by project sharer and it supports setting params yay)</strong></li>\n<li>There’s UI for adding a param to a ticket <strong>(yes, you edit the ticket and can set any workflow param)</strong></li>\n<li>There’s UI for removing a param from a ticket <strong>(yes, you can set an enum param to None and a text param to empty string, which makes them appear unset in UI)</strong></li>\n<li>There’s UI for editing a ticket’s param <strong>(yup, in ticket edit form)</strong></li>\n<li>In ticket page, the params are displayed in a sane manner, and there are buttons/links/UI for editing/removing the params, and button/link/UI for adding new params <strong>(UI for editing params is in ticket edit page, good enough for now; display is minimally usable)</strong></li>\n</ul>\n<p>It seems to work, but how do we get that nice colorful label display that forges usually have?</p>",
    "replies": "https://vervis.peers.community/decks/br6Go/tickets/EZQOv/discussion",
    "isResolved": false,
    "followers": "https://vervis.peers.community/decks/br6Go/tickets/EZQOv/followers",
    "source": {
        "mediaType": "text/markdown; variant=Pandoc",
        "content": "Check the following:\n\n- Who should be able to set/unset issue labels by default, when creating issue and when editing? Who's allowed to do that in NAB / Gitea? Issue author? Repo team? Both?\n\nImplement the following (or verify that it's implemented and works):\n\n- When editing a project, either the workflow can't be changed, or a workflow change involves a check whether any tickets use the current workflow **(workflow can't be changed)**\n- When editing/deleting a workflow field, it checks whether any tickets use that field or the values being changed/deleted **(field, enum and ctor deletion and editing not implemented)**\n- Ticket params can only be set according to roles; add a role operation for this if needed **(ticket creation doesn't allow to set params; ticket editing allowed only by project sharer and it supports setting params yay)**\n- There's UI for adding a param to a ticket **(yes, you edit the ticket and can set any workflow param)**\n- There's UI for removing a param from a ticket **(yes, you can set an enum param to None and a text param to empty string, which makes them appear unset in UI)**\n- There's UI for editing a ticket's param **(yup, in ticket edit form)**\n- In ticket page, the params are displayed in a sane manner, and there are buttons/links/UI for editing/removing the params, and button/link/UI for adding new params **(UI for editing params is in ticket edit page, good enough for now; display is minimally usable)**\n\nIt seems to work, but how do we get that nice colorful label display that forges usually have?"
    },
    "id": "https://vervis.peers.community/decks/br6Go/tickets/EZQOv",
    "type": "Ticket",
    "attributedTo": "https://vervis.peers.community/people/VvM9v"
}