HI, Can i use components to help with post deployment? for example all "UI" issues completed can be catorised with components and allocated to our post deployment team to update for example training guides and documentation? but ie. "BACKEND" component can just be part of the release notes because it did not have any direct impact on the operational or support teams
Pretty terrible advice "use the field for whatever you want"... in a 10k person company, that is disastrous advice, the things I've seen man... better advice would be "restrict the components to the actual application hierarchy so it sorts naturally", unfortunately I don't think the feature offers a hierarchy of component approach, so it's actually pretty useless and tends to devolve into a flags field as described.
You aren't going to like the direction Atlassian is going then. There is going to be a lot less structure and a whole lot more do whatever you want once they merge Jira Software and Jira Work Management.
@ApetechTechTutorials yeah, think it's time to switch back to Ms projects or just excel... can't really use jira for any projects of significant criticality, I mean Atlassian typical ticket response time is 5 years from what I've seen, so ultimately their bar is very lower on the basics of workforce management.
HI, Can i use components to help with post deployment? for example all "UI" issues completed can be catorised with components and allocated to our post deployment team to update for example training guides and documentation? but ie. "BACKEND" component can just be part of the release notes because it did not have any direct impact on the operational or support teams
Thank you for this video
My team mostly use Label and never used Component. What is the main difference between and when should you use which.
Label, anything goes. With Component, you can define those values for your team and they get to pick from a drop down that is now controlled by you.
I find it interesting that the auto assign is only working on create, not on update...
I don't have components option in project settings
You probably have a team-managed project?
Than😊
Don't forget team managed projects cant create components even if you are an admin
Pretty terrible advice "use the field for whatever you want"... in a 10k person company, that is disastrous advice, the things I've seen man... better advice would be "restrict the components to the actual application hierarchy so it sorts naturally", unfortunately I don't think the feature offers a hierarchy of component approach, so it's actually pretty useless and tends to devolve into a flags field as described.
You aren't going to like the direction Atlassian is going then. There is going to be a lot less structure and a whole lot more do whatever you want once they merge Jira Software and Jira Work Management.
@ApetechTechTutorials yeah, think it's time to switch back to Ms projects or just excel... can't really use jira for any projects of significant criticality, I mean Atlassian typical ticket response time is 5 years from what I've seen, so ultimately their bar is very lower on the basics of workforce management.