Hi,
I'm planning to create a screen, say "Raise SO" to capture all the details required for a sub asset type
for e.g. A new user joins the company. So a new request line willl be created for this user and all the assets required for this user will have sub task lines. i.e. For a phone, Laptop etc...
Each subtask will have its own type properties / attributes to capture for e.g. Phone will have brand, OS version, LeadTime etc... while Laptop will have its own properties like Brand, Memory etc.
How are situation like this handled in Jira - do we create Task and subtask? What are the other approaches, if any? Since this screen will be part of the WF at a certain stage, do I need to create a seperate queue to see the details of this subtask?
Appreciate the help and feedback.
Thanks
Hi @S,
There's no "the" right way to do this.
I hope that this helps.
Thanks,
Moga
Thanks @mogavenasan
I have defined my custom request and issue types so can I harness Task and Sub-task hierarchy? I liked the way its laid out.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Glad to know that!
Please mark this thread as solved if you do not need any further assistance. :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.