[release-4.13] CONSOLE-3452: Add patternfly customer feedback extension mechanism to console #12637
Conversation
Update json file for localization. Added yarn.lock file for dynamic plugin. Updated share-feedback, join mailining list URLS Added code to switch label and description for report a bug.
|
@openshift-cherrypick-robot: An error was encountered cloning bug for cherrypick for bug CONSOLE-3452 on the Jira server at https://issues.redhat.com/. No known errors were detected, please see the full error message for details. Full error message.
request failed. Please analyze the request body for more details. Status code: 400: {"errorMessages":["Number value expected as the Sprint id."],"errors":{"customfield_12318341":"Operation value must be a string"}}
Please contact an administrator to resolve this issue, then request a bug refresh with In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
openshift-ci
bot
added
component/core
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: dlabaj, openshift-cherrypick-robot The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/hold Hi, what is the rationale for backporting? We are past feature freeze and should only backport bug fixes. |
openshift-ci
bot
added
the
do-not-merge/hold
|
@dlabaj @spadgett the pr is linked in US https://issues.redhat.com/browse/CONSOLE-3452. I've tested it and no issue is found. Is it a valid pr? If yes, I will add qe label for it. |
|
@spadgett The thought was that this might be helpful in getting user feedback data for the tech preview version of multi cluster, and that the change might be small enough to backport in to 4.13. If you think this is of significant priority and is small enough to back port then we can move forward with this (by creating the necessary bug to backport into 4.13). Otherwise I can delete this pr and keep the feature in 4.14. cc: @jhadvig |
|
/retest |
|
@openshift-cherrypick-robot: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
@spadgett Here's a thread with rationale for backporting from @showeimer. If this is low-risk enough, being able to prioritize and act on feedback from 4.13 users before their next upgrade should be worth it. cc @alimobrem |
|
@jcaianirh Can we close this? |
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
openshift-ci
bot
added
the
lifecycle/stale
|
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
openshift-ci
bot
added
lifecycle/rotten
|
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
|
@openshift-bot: Closed this PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This is an automated cherry-pick of #12611
/assign jcaianirh