I would like to add a custom data view within my Jira project. The purpose of this would be to list delivered software versions in the field to track which versions are installed on different machines. Manual update of the data is fine. Alternatively is the "Release" area capable of being updated with this information and to display it is a collated fashion (list by tool ID).
A table would be fine and I did try the table grid plugin but it only seems to be able to add a grid within issues whereas I would like to do this at the project level without associating any given tickets.
Is this possible?
Thank you very much for the quick reply on this. I've downloaded the trial of ProFields. It's very very close to doing what I would need.
Basically I will have a list of Machines with customers and for each of those machines I have a standard set of field values to list.
Using Profields I initially thought this would work fine if I treated each machine as a Container in a view. I can use the sections to split out different customers and in each container I though I could have the information relevant to each given machine.
The snag I've hit though is that fields seem to be use once. So once they exist in one container I can't use them again in another. Is there any way around this limitation? Essentially if I could copy/paste a common container structure and fill in the values all to appear on the same screen I would be happy.
Failing that is there another way of using profields you could suggest to achieve what I'm trying to do?
Thank you again
Happy to help you!
At this time the only way to solve your needs will be as many customer and machine tracking fields as you need, as long as you can limit the number of customers and machines per project. Is it possible? Profields doesn't have any problem to manage 20, 30 or 40 fields....
Hope to help you!
I've checked with the trial just to confirm that multiple fields can have the same name and it looks like they can so I can probably work with this. Definitely going to be a long setup though I'm probably looking at around 80 fields in total with probably future additions as we deliver more machines.
Is there any way I can record a suggested/requested future feature to support easier copying/duplication in future?
Either way you have given me a solution to the immediate problem so thank you very much for that.
Thank you for the reply. There isn't really any direct connection with issue fields in this case. I'm investigating the plugin from the suggestion above and failing that I will look more at confluence. Initially it looks like overkill for the specific feature I'm looking for but it may end up being necessary.
Really appreciate your quick response though thank you,
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events