This idea has been archived, contributions have been disabled 

We think that this idea is good and we’d like to take a better look at what the needs are behind and/or how it could fit into our current product strategy.

However the linking will probably be done in the new planning tools rather than in Tasks, hence the status of this idea...

Comments (8)

Robert B Johansson
Robert B Johansson

Robert B Johansson

Level
0
Score
0

I like this idea.

Bethany Payne
Bethany Payne

Bethany Payne

Level
0
Score
0

Good idea. It would save a lot of time and worry.

Joachim Schirra
Joachim Schirra

Joachim Schirra

Level
1
Score
141

Agree absolutely. It is logical. You have issues, which are not identical with tasks. If they were, then you needed no issues. Issues differentiate by the fact, that they are not assigned directly to somebody.

Option 1: In the moment you assign a ressource to the issue, the issue is converted to a task and the issue is deleted/cancelled.

Option 2: The issues always will be existend unless the status is not set to "resolved". But then the requested functionality to link it to a task is more than logical.

Unimportant which of both opitions projectplace decides to follow, as long as not one of both options is implemented in projectplace, there will be an inconsistency.

Hope, you consider this also as being necessary. Go for it, you can. ;-)) Time for a change. ;-)

Regards,

Joachim Schirra

silvio regazzoni
silvio regazzoni

silvio regazzoni

Level
0
Score
3

Exactly Joachim!
I was just about to write an idea covering a combination of 1 and 2. When an issue is assigned to someone AND there is a due date you should be able to get the possibility to create an activity (or rule-based automation). I think there should also be an interaction back and forth between issues and activities. An issue typically generates an activity that is followed by one or more actitvities that all map to a set of worksteps and issue statuses. F ex. Requirement-Specification-Design-Develop-Test-Deliver-Operate-Support. The basic issue may still be one, but a bunch of sequential (and also possibly some parallell) activities ensue.

Anonymous
Anonymous

Anonymous

Level
0
Score
0

Very important idea! It would be very efficient if you could create and follow-up Issues in the "Task-view" for each sub-task. You then introduce more understanding of what you do in your project and where you are within the completion of each task. As mentioned in previous comments: you need to complete several Issues to complete a Task. The connection is obvious, but today both these views seems to live their own lives....A lot of hard work to use both tools according to me and my collegues. It is hard to motivate people to use Issues. Using the Task view is easier to motivate since it is obvious that we need to structure the project and follow-up the degree of completion in each sub-task, to be communicative (at least). Why not do all follow-up in the same view, keep it together and get it more understandable?

We think that this idea is good and we’d like to take a better look at what the needs are behind and/or how it could fit into our current product strategy.

However the linking will probably be done in the new planning tools rather than in Tasks, hence the status of this idea...

Anonymous
Anonymous

Anonymous

Level
0
Score
0

Hello,
There are other ideas which cover more or less the same issue.
For example:
http://ideas.projectplace.com/feedbacks/46568-improvement-idea-better-link-between-tasks-and-documents
and
http://ideas.projectplace.com/feedbacks/46259-link-to-documents-from-the-task-arbeidsoppgaver-window

@Support Project Place could these not somehow be linked?
This would improve the use of this ideas functionality and give you a better insight of what is required.
Kind regards
Paul Bergman

DIMELO - SocialCRM software editor