Parent Field Plugin

Cool.  is this doing what I think it's doing => copying the parent's field value to a field on the subtask?

I really hope the answer is YES!

This looks really nice as a stop gap to being able to search by parent field.

 I've installed it, but the field I want to display (Fix Version/s) doesn't work.  I wonder if its because of the Space and / in the name, or is it the data type?

Thanks Mike, that sorted it, but now I have another need - I'm using Priority as a parent field.  It works, sort of, but Parent Priority is displayed as a fairly ugly string.  I suppose you'd need to work out the correct display template to display the icon somehow.

hi,

Where is the jar and source?

thanks

Awesome plug-in. I have been looking for something like this for a while.

I did run into one issue however; it doesnt seem to work with Cascading Select fields.

Any chance of getting this fixed?

Thanks again! 

How do you configure the screens to display the parent fields ?

... forget about it, found it.

You need to add custom fields with the name as indicated in the explaination

Mike, does this plugin allow the user to filter on the "ParentXXX" field?  Or just to sort by that field?  For example, could I filter for all issues for which the value of "ParentXXX" is "XYZ"?  I'm looking for a way to filter using fields from both the parent and its sub-tasks.

Hi Mike,

First of all, thanks for writing this!  We also need the ability to filter by values in the Parent FixVersion field.  Are there any plans to make this functionality available?  I'm assuming that this is a non-trivial effort since I don't see any actual values in CUSTOMFIELDVALUE for Parent FixVersion.

 Secondly, is it possible to post the source code?

Thanks Again!

Chris Dewey

Very helpful, thank you!

One wrinkle: a Parent IssueType renders as:

[GenericEntity:IssueType][id,1][style,null][description,A problem which impairs or prevents the functions of the product.][sequence,1][name,Bug][iconurl,/images/icons/bug.gif]

rather than just "Bug".

This plugin is just what we are looking for. However, we have a number field for which we cannot get it to work. It appear to know that there is a value in the parent field, but nothing is displayed.
Is this a known issue/limitation or an incompatibility with Jira 3.12

This plugin caters to my need exactly . I have installed this plugin on my JIRA , but when i create field like Parent Summary , Parent Description etc , i dont see them on the child . I am on version 3.12.1 . Also I am using it for some of the issue types like Bug , User Story etc . But not for TAsk . Though I am sure the issue type shuld not hinder the functioning as long as it has the parent child realtionship , could you let me know or give a fix for the same . It will be highly appreciated

Thanks in advance

I am trying to use this on a user field and it seems to put an empty value in the field. Does anyone know a work around?

I found a bug in this plugin, when you clone an issue with its sub-task that have "Parent" fields you get an exception.

2008-04-29 13:53:03,887 http-80-Processor57 ERROR [atlassian.jira.workflow.SimpleWorkflowManager] Error occurred while creating issue. This could be due to a plugin being incompatible with this version of JIRA. For more details please consult the logs, and see: http://confluence.atlassian.com/x/3McB
java.lang.ClassCastException: com.opensymphony.user.User
        at com.princeton.jira.plugin.parentfield.ParentFieldCFType.getStringFromSingularObject(ParentFieldCFType.java:46)
        at com.atlassian.jira.issue.customfields.impl.StringCFType.getDbValueFromObject(StringCFType.java:20)
        at com.atlassian.jira.issue.customfields.impl.AbstractSingleFieldType.createValue(AbstractSingleFieldType.java:117)
        at com.atlassian.jira.issue.fields.CustomFieldImpl.createValue(CustomFieldImpl.java:574)
        at com.atlassian.jira.workflow.function.issue.IssueCreateFunction.execute(IssueCreateFunction.java:85)

After you get the error it will clone the sub-task but orphan it with out a parent task, then when you move it to its new cloned parent you get the same error.

Hi Mike!

I was testing the plugin and it seems to work fine with text fields, but when i try to show a "date" or "date-time" field from the parent into the subtask field, nothing happens. The field remains blank.

Do you have any idea of what is the problem!? 

Thanks in advance for your help!

Regards,

Irene 

To enable searching for any parent field that is simple text you can do the following.

1 - download and extract the parent field jar from above

2 - open the file atlassian-plugin.xml in the root folder

3 - Add the following text below to the file. Insert this after:  </customfield-type>, which is at line 16.

    <customfield-searcher key="textsearcher" name="Free Text Searcher"
        i18n-name-key="admin.customfield.searcher.textsearcher.name"
        class="com.atlassian.jira.issue.customfields.searchers.TextSearcher">
        <description key="admin.customfield.searcher.textsearcher.desc">Search for values using a free text search.</description>
        <resource type="velocity" name="search" location="templates/plugins/fields/edit-searcher/search-basictext.vm"/>
        <resource type="velocity" name="view" location="templates/plugins/fields/view-searcher/view-searcher-basictext.vm"/>
        <valid-customfield-type package="com.princeton.jira.plugin.parentfield" key="parentfield"/>
    </customfield-searcher>

4 - Create a new jar file: jar cvf parent-field-0.2.jar *

5 - Install the jar just like normal by copying to the jira lib folder. 

6 - Stop and start Jira.

7 - Now when you go to add a custom field using the Parent Field type you will see that a search template is now available, it will be the free text search. Make sure you choose this.

8 - IMPORTANT: You will now need to re-index Jira. Go to the admin section, index, and then click the re-index button.

You will now be able to search based on your parent field custom field types. I have only tested this using a custom of field of Parent Key. It should work with any parent field that is a simple text field. It won't work with more other data types though, although you may get lucky and have it work, but I have only tested it with simple types.

This plugin would be more useful with its source code, we cannot rely on an unmaintained and closed source plugin