You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have not been able to find my answer for 100% in the search.
We have got project, which works like reporting for internal purposes - vacation, sickness, etc.
So I have created some tasks, which can be chosen when creating, but then i needed to show under certain tasks subtasks which will be connected to this certain task:
Task: Absences Sub-taks: Vacation, Doctor, Sickness etc... So, that the reporter can easily pick from what is the thing, he is reporting. But right now he can create only tasks - probably due to my bad settings and when the issue is created, he can create sub-task for any task there is. Which is basically not something we need. As difficult as this is, there is another issue for this which is that we need certain tasks have different fields - which brings me to my next question.
Do I need to setup for every different task connected to different field screen, so that it would work properly?
And then again, how will it look, when you are gonna have this used and you will look under project settings > Screens?
Ok, so you're definitely looking for something that you can't do.
A sub-task can be created under any issue type you have in the project. The parent issue type cannot limit the sub-task types your users can create beneath it. The issue types available to a project are done at the project level.
So what approach would you suggest if I would need to have one parent issue type (for example Abscences) and then few child issues (doctor, vacation etc.)? Because if you are not able to connect certain sub-task to parent issue type, then what is the point in having more child issue types? Do you got my point?
Is there even any possibility how to approach this?
I could probably make field in which one would be parent type and second child issue type as I am trying to reach... But there is as well the field dependency, which will say to system, that when parent issue is lets say Abscences, you can only choose from certain types of child issue and not from all of them...
Field Type Select list - single choice Name: Request; and you can choose from:
Field Type Select list - single choice Name: Type of request
New invoice etc
And then when you choose the first field it will change the choices in the second one...
I belive you got my point.
Why are you representing information about an absence with a sub-task? That sounds like a broken data model to me.
Surely an abscence is a time-box, which would have a start date, end date and a simple type (which you could do as the issue type, or by a select list if you wanted to just have a generic "not here" type that you can later classify as sick or holiday or doctor visit or or or)
It is an odd one, it's well worth questioning the requirement. There's something here that I suspect is going to be "we want to be able to report on time taken up by various things", but that might be better done with work logs on tasks that are dedicated to it.