Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 341307

Summary:	Support local tasks as subtasks of repository tasks
Product:	z_Archived	Reporter:	Chris Beams <cbeams>
Component:	Mylyn	Assignee:	Mylyn Inbox <mylyn-inbox>
Status:	CLOSED MOVED	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	cbeams
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:
Bug Depends on:
Bug Blocks:	354528

Description Chris Beams

2011-03-30 02:05:13 EDT

Build Identifier: 

I will use JIRA as an example repository here, but the requested feature is equally applicable to all task repositories.

1. I am working on a JIRA issue via Mylyn, SPR-1234: "Support excellent new feature"
2. I decompose my work into fine-grained local tasks as I go.
3. I would like to drag those local tasks onto my SPR-1234 repository task to express their parent-child nature.

This is currently not possible.  Note that I am creating local tasks instead of repository subtasks because in many cases, the tasks are simply TODOs and reminders during development that don't merit exposing to the outside world.  They are often resolved so quickly that creating an actual remote issue is simply overkill.

Hopefully this is something that the Tasks Framework can handle generically, as opposed to being something to implement on each connector (JIRA and otherwise).  From my uninitiated point of view, it seems like a relationship hanging off Mylyn's notion of a repository task, not something that actually needs to be communicated or supported server side in the repository (the whole point is to avoid talking to the repository...)

Thanks for considering,

- Chris Beams

Reproducible: Always

Comment 1 Chris Beams

2011-03-30 11:14:23 EDT

Related to this, it would be equally as excellent to allow local tasks to be grouped under repository queries.  I can create a separate issue for this, but thought I'd throw it in here during the initial gathering of feedback.

Ideally, this would work just like Task->Set Category works now.  Either a separate menu item ("Set Query", perhaps), or Queries just show up under the list of available categories during a Task->Set Category action.

For a concrete use case, right now I have to maintain a repository query called "Spring 3.1 Major Themes and Features" for everything that's actually in the Spring JIRA repository, as well as a "Spring 3.1 Major Themes and Features for local issues that I have not yet put in the repository due to reasons of being offline, or because the feature isn't well-enough thought out yet.  This is but one of many such Query / Category splits I maintain.  Simply assigning a local task to a repository query would solve the issue completely.

Thanks.

Comment 2 Steffen Pingel

2011-08-15 11:05:32 EDT

Thanks for your request. I think there are several aspects to this. One is being able to associate a task with other tasks. Third party extensions such as Tasktop offer this support already. I am wondering if check lists would be another way to solve the described requirements. A check list would essentially be a list of very light weight subtasks of another task. A little more discussion is on this bug (behind sign-up) [1].

Another aspect is how to show these relations in the task list. Currently the task list is (mostly) limited to showing subtasks but we have discussed extending that on bug 232222. My sense everything shown under a query should be matched by it in order to keep the task list manageable. If we allow other associations such as related tasks this could easily overload the task list. I could imagine multiple presentations though that show different structures as we already do with the scheduled and categorized presentation.

Would you be able to file another bug for comment#1? I am wondering if this could be solved by showing unsubmitted repository tasks under queries.

[1] https://live.tasktop.com/dev/bugs/show_bug.cgi?id=1715

Comment 3 Eclipse Webmaster

2022-11-15 11:45:08 EST

Mylyn has been restructured, and our issue tracking has moved to GitHub [1].

We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub.

[1] https://github.com/orgs/eclipse-mylyn