We are enrolling the use of Jira Assets into our organization. One of the use cases is to replace (and migrate) custom nFeed fields within Jira Software towards Jira Assets. We have some Objects defined within Jira Asset for which we are not able to use them in the Jira Software Application (f.e. Boards) and/or Plans (former Advanced Roadmaps). Below some more information on the use case can be found below.
Is there any configuration, integration and/or feature on the roadmap to enable the use of Jira Asset objects in Jira Software?
Use case:
An Object (Quarters) was created for the end-user to indicate on which Quarter the work is being done (see screenshot). Currently we are not able to use these objects in the Configuration of our Boards (see screenshot 2) nor in Plans (see screenshot3)
Also looking for this feature. We're trying to use Assets/JSM in our organization and keep running into these blocking limitations. For instance, we want to be able to group issues in our plans by the value in an asset field so that we can look at scheduling/utilization. We're currently using Components as a "hack" for that, but realistically we should be using the actual Asset since that ties into JSM and are cross-project.
You can try voting for the feature here: https://jira.atlassian.com/browse/JSWCLOUD-20382
I would vote for this feature also. We are modeling Agile concepts like "Product", "Value Stream", "Release Train", etc. using Assets. It would be amazing if these could then be selectable in Plan views.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We have the same problem, I would greatly appreciate suggestions :--)
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.