Hi,
For each of our parent bugs, we create sub-task of type "backport request". Each backport request corresponds to a release branch. There is a separate workflow for the backport request.
When I search using jql, I get results of parent bug. For each of the parent bug, i would like to see the status of their backport request in the filter results. Is there a way to add a column in the search result that will pull data from the backport request and display ?
Hello,
You can use the Power Custom Fields plugin to create a custom field, which would provide the required info. Then you can add this custom field to the search result.
https://marketplace.atlassian.com/apps/1210749/power-custom-fields?hosting=server&tab=overview
Or you can use ScriptRunner or Nfeed.
we already have custom fields in our jira project. When I go columns in search result, I can search for the custom field and i can add it but do I need the plugin to choose the field corresponding to backport request ?
For example, we have a custom field called "Target Fix Version". But this field is both in Parent bug as well as in the backport request. In my search result (which displays parent bugs), I want to add the "Target fix version" from backport request.
Do I need this plugin for this ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Each line in your search result gives you the fields that are for the issue being listed. You are asking to see fields from *other* issues than the one being reported, which is not what most people would expect to happen
What Alexey is suggesting is that you expose the "backport request" field as though it is part of the parent. Jira doesn't do this off the shelf, so you need code that can read the sub-task and pull the data into a field on the parent (Script Runner, Power Scripts, Automation, Power custom fields, Nfeed, all can do this sort of thing)
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.