[
https://issues.apache.org/jira/browse/SQOOP-1689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350533#comment-14350533
]
Jarek Jarcec Cecho commented on SQOOP-1689:
-------------------------------------------
Umbrella JIRA is used to cover bigger feature or bug that is broken to
independent subtasks that are committed independently [~vybs]. In majority of
cases umbrella JIRA do not have a patch by itself as it serves only as place to
gather relevant subtasks together. It's also resolved only after all it's
subtasks are resolved (~ feature/bug fix is completely done).
If you need to link related tickets together to keep track of them, you should
use the "Link" option from "More" menu. I've actually done that with this one -
I've broke the subtask relationship and added link of type "is related to". By
linking two JIRAs, both of them will get new section "Issue Links" and you can
easily see what all tickets are related. There are multiple different Link
types (depends, is broken by, ...) which helps to explain the kind of link
between the two JIRAs and hence it's better facility to connect related JIRAs
then subtask.
> DOC: update for Rest API and Shell commands for Read/Edit config inputs
> -----------------------------------------------------------------------
>
> Key: SQOOP-1689
> URL: https://issues.apache.org/jira/browse/SQOOP-1689
> Project: Sqoop
> Issue Type: Bug
> Reporter: Veena Basavaraj
> Assignee: Veena Basavaraj
> Fix For: 1.99.6
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
