Join the community to find out what other Atlassian users are discussing, debating and creating.
Where do you put the platform information in issues. As far as I can see there are tree options.
- fixVersion
- Components
- Custom field
We have three platforms phone, tablet and web. The product is different on each. But the phone and tablet app is the same file (UI changes run time)
Where do you keep the info?
What would you suggest to me?
Fix Version/s is of Version Picker type. It generally indicates to your repository version.
Component/s is of multi-select type. It generally indicates to your project module.
There is also Labels field which is of Labels type. It generally indicates the type of issue.(e.g what we place here jira-agile related question in answers)
Custom Field could be based on the requirement, we choose the appropriate type. For your requirement, Select List is good if you choose only one platform at a time otherwise Multi Selct is good if you choose multi platforms.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So which one do you use? What would you recomend?
We don't use components as project modules, we leave that for epics. Components are backend, frontend asf. Things that end up between features (modules). I see it as a way to sort stuff across features, as i.ex. platform.
I thought Version was the version it needed to be finished with. Sort of a deadline and a group of tasks that comes out in a release.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Jenkins is the leading open-source automation server used by startups and enterprise teams to build, test and deploy code to production. We are excited to announce an official integration betw...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.