bugwarrior icon indicating copy to clipboard operation
bugwarrior copied to clipboard

Gitlab: work items

Open rubdos opened this issue 1 year ago • 3 comments

Gitlab recently introduced Work Items, used to subdivide issues into smaller tasks.

I've started using them on Gitlab. While they get assigned identifiers in the same space as issues (so, work items numbers are just issue numbers), they don't show up in Bugwarrior. It would be nice if they could show up. Additionally, bugwarrior could also register the dependencies between a work-item and its parent issue!

rubdos avatar Oct 17 '23 12:10 rubdos

I've looked a bit around:

work_items is the generalization of issues/tasks/epics etc:

Work Item types

A set of predefined types for different categories of work items. Currently, the available types are:

[Incident](https://docs.gitlab.com/ee/operations/incident_management/incidents.html)
[Test case](https://docs.gitlab.com/ee/ci/test_cases/index.html)
[Requirement](https://docs.gitlab.com/ee/user/project/requirements/index.html)
[Task](https://docs.gitlab.com/ee/user/tasks.html)
[OKRs](https://docs.gitlab.com/ee/user/okrs.html)

Work is underway to convert existing objects to Work Item Types or add new ones:

[Issue](https://gitlab.com/groups/gitlab-org/-/epics/9584)
[Epic](https://gitlab.com/groups/gitlab-org/-/epics/9290)
[Ticket](https://gitlab.com/groups/gitlab-org/-/epics/10419)

What I actually wanted to see in BW are Gitlab tasks, but tasks are currently not API-exposed.

rubdos avatar Oct 17 '23 15:10 rubdos

Hopefully gitlab releases a new api that uniformly exposes all the Work Item Types. In the meantime, are Work Items themselves API-exposed yet? (That is, is this issue actionable?)

ryneeverett avatar Oct 17 '23 18:10 ryneeverett

That is, is this issue actionable?

I don't think it's currently actionable, no, from my very quick glance over the docs and some experimenting.

rubdos avatar Oct 18 '23 09:10 rubdos