Hi Kumar,
adding to the good suggestions of Nic and Jack I'd like to pass around the relevant sections of documentation in case you are interested in further reading.
This won't go into the detail as of the "why" there is a "Job Story" Issue Type present in your instance but it gives a nice overview about the terminology "Issue Type" and the differentiation to a Custom Field. Enjoy!
Regards,
Daniel
Yes, it is a Custom field. But in my project ,I have seen many stories with this issue type. So just want to check if anyone knows about it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Issue type is not a custom field, it's a system field, and a structural one.
I would say Jack is right - for some reason, someone in your organisation has added an issue type called "job story". You'll need to ask them what it's for (and as it's lead to you questioning it, I'd recommend having a conversation about why they've used a name you had to question)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Where have you been hearing this? My suspicion here is that this is simply a custom issuetype that has been created in your instance or possibly another instance. If so then the meaning needs to be stated by the one that created. Please share more info.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I would suggest talking to your admin to understand when one might use simply Story vs the custom Job Story.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.