What we currently have with issue relations is great. Yay!

...but I just spent quite some time moving a dozen issues from the "related issues" subsection in an issue summary (#1986434: New visual style for Seven) to the dedicated section we now have in the issue metadata only to find out that these were added as related/referenced-by. Problems with that:

a) There is no way to convert these relations to a parent/child relation instead.
b) The *only* alternative to create parent/child relations is to edit each child issue and add the parent issue in their metadata section. This gets really tedious when you have a lot of child issues to add.

What I propose is that we should implement one of the solutions below:

1) we have a drop-down next to each autocomplete that allows to select the type of relation of the entered issue to the issue being edited.
2) we have some sort of related/child separator (the way we have the visible/hidden in the manage display of fields) so we can drag issues to become either one of these allowed types of relations.
3) other thoughts?...

Comments

klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
CreditAttribution: klonos commented
Issue summary: View changes
klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
CreditAttribution: klonos commented
Parent issue: » #2125117: [meta] Adding related issues needs major improvements
klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
CreditAttribution: klonos commented

...actually people seem to be highjacking either the parent issue filed or the related issues in order to find a place for duplicate issues (#2132229: Provide a "Duplicate of:" / "Duplicate issues:" two-way relation for issues.), so what I propose in the issue summary (either a drop-down with the type of relationships or being able to drag-n-drop related issues' rows to separate related/children/duplicate sections) should include duplicate issues too.

eliza411’s picture

eliza411 CreditAttribution: eliza411 commented
Issue tags: +D.o UX

Tagging.

mgifford’s picture

mgifford
he/him
Primary language English
CreditAttribution: mgifford commented

A drop-down with the type of relationships would make sense to me. Would make it more flexible moving forward.

I like the idea of having a specific field to specify a duplicate.

tvn’s picture

tvn CreditAttribution: tvn commented
Project: [Archive] Drupal.org D7 upgrade QA » Project issue tracking
Version: » 7.x-2.x-dev
joachim’s picture

joachim CreditAttribution: joachim commented

That's going to require a whole new field widget -- more than that in fact, as related issues and parent issues are two different fields, so what's being described here is an entityreference field widget that covers more than one field. That's going to be pretty complicated.

In the meantime, here's a simpler proposal for part of what's requested here: #2426711: Add a link to create a child issue to the child issues block