Uploaded image for project: 'Advanced Roadmaps'
  1. Advanced Roadmaps
  2. JPOSERVER-2268

Updating portfolio custom fields in plan does not trigger indexing (does not update issue's updated date and does not trigger updated issue event)

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: High High
    • 2.17.0
    • None
    • Plan
    • None

      Summary

      Updating portfolio custom fields in plan does not update issue's updated date.

      Steps to Reproduce

      1. Go to the plan
      2. Set value to Portfolio custom fields (such as Target Start, Target End, Team) for issues in the plan
      3. Go to those issues

      Expected Result

      Issues will get updated (updated date field is updated) and updated event is not triggered.

      Actual Result

      Issues does not get updated (updated date field is not updated), Updated event is not being triggered, and indexing is not triggered.

            [JPOSERVER-2268] Updating portfolio custom fields in plan does not trigger indexing (does not update issue's updated date and does not trigger updated issue event)

            Thomas added a comment -

            Hi swarna.radha1448355391,

            Can you please ensure that:

            1. You are using Portfolio 2.16.0
            2. History is being generated in the issue

            It's possible that while Portfolio should now be triggering the right event and generate history, notifications are not? If that's the case, knowing the version of Jira you are using could help.

            Thomas added a comment - Hi swarna.radha1448355391 , Can you please ensure that: You are using Portfolio 2.16.0 History is being generated in the issue It's possible that while Portfolio should now be triggering the right event and generate history, notifications are not? If that's the case, knowing the version of Jira you are using could help.

            Hi @Thomas,

            No notification is triggered when Target Start and Target End are updated.

            Swarna Radha added a comment - Hi @Thomas, No notification is triggered when Target Start and Target End are updated.

            Thomas added a comment -

            Hi all,

            History for Target Start and Target End fields has been fixed in our 2.16.0 release, other fields are still a work in progress and will be resolved as part of a future release.

            This issue will be marked as resolved once the other fields are actually fixed.

            Thomas added a comment - Hi all, History for Target Start and Target End fields has been fixed in our 2.16.0 release , other fields are still a work in progress and will be resolved as part of a future release. This issue will be marked as resolved once the other fields are actually fixed.

            Hi,

            When the functionality will release?? Any feedback..

            Please give this a high priority!

            Swarna Radha added a comment - Hi, When the functionality will release?? Any feedback.. Please give this a high priority!

            Hi, we have big issues due to this. Our updated date is now unreliable for a variety of purposes.

            Please give this a high priority!

            Ian Clelland added a comment - Hi, we have big issues due to this. Our updated date is now unreliable for a variety of purposes. Please give this a high priority!

            Within ABN AMRO we have lots of issues with this bug! we cant make good filters on target end and target start date! Please give it a an high Priority in solving this issue. 

            Dennis Struis added a comment - Within ABN AMRO we have lots of issues with this bug! we cant make good filters on target end and target start date! Please give it a an high Priority in solving this issue. 

              tbarthelemy Thomas
              azuhra Aqqiela
              Archiver:
              atibrewal@atlassian.com Aakrity Tibrewal

                Created:
                Updated:
                Resolved:
                Archived: