Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Admin - dropdown toggle arrow not working on closing #20240

Closed
saphaljha opened this issue Jan 12, 2019 · 10 comments
Closed

Admin - dropdown toggle arrow not working on closing #20240

saphaljha opened this issue Jan 12, 2019 · 10 comments
Assignees
@niravkrish
Labels
Component: Ui Fixed in 2.2.x The issue has been fixed in 2.2 release line Fixed in 2.3.x The issue has been fixed in 2.3 release line Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release

Comments

@saphaljha
Copy link
Contributor

Preconditions (*)

  1. Magento 2.3

Steps to reproduce (*)

  1. Add/Edit any product
  2. Click on any dropdown and again click on it closing it.
  3. Array will not rotate on closing

Expected result (*)

acpected-productsinventorycatalogmagentoadmin

Actual result (*)

actual-productsinventorycatalogmagentoadmin
@magento-engcom-team
Copy link
Contributor

magento-engcom-team commented Jan 12, 2019 •
edited by niravkrish
Loading

Hi @saphaljha. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

  • Summary of the issue
  • Information on your environment
  • Steps to reproduce
  • Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento-engcom-team give me $VERSION instance

where $VERSION is version tags (starting from 2.2.0+) or develop branches (for example: 2.3-develop).
For more details, please, review the Magento Contributor Assistant documentation.

@saphaljha do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

  • yes
  • no

@magento-engcom-team magento-engcom-team added the Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed label Jan 12, 2019
@saphaljha saphaljha self-assigned this Jan 12, 2019
@shikhamis11 shikhamis11 self-assigned this Jan 12, 2019
@niravkrish niravkrish self-assigned this Jan 12, 2019
@magento-engcom-team
Copy link
Contributor

Hi @shikhamis11. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

  • 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

    DetailsIf the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

  • 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

  • 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

  • 4. Verify that the issue is reproducible on 2.3-develop branch

    Details- Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
    - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

  • 5. Verify that the issue is reproducible on 2.2-develop branch.

    Details- Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

  • 6. Add label Issue: Confirmed once verification is complete.

  • 7. Make sure that automatic system confirms that report has been added to the backlog.

@magento-engcom-team
Copy link
Contributor

Hi @niravkrish. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

  • 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

    DetailsIf the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

  • 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

  • 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

  • 4. Verify that the issue is reproducible on 2.3-develop branch

    Details- Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
    - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

  • 5. Verify that the issue is reproducible on 2.2-develop branch.

    Details- Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

  • 6. Add label Issue: Confirmed once verification is complete.

  • 7. Make sure that automatic system confirms that report has been added to the backlog.

@saphaljha
Copy link
Contributor Author

@magento-engcom-team give me 2.3-develop instance

@magento-engcom-team
Copy link
Contributor

Hi @saphaljha. Thank you for your request. I'm working on Magento 2.3-develop instance for you

@magento-engcom-team
Copy link
Contributor

Hi @saphaljha, here is your Magento instance.
Admin access: https://i-20240-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

@saphaljha saphaljha added Component: Ui Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed labels Jan 12, 2019
@magento-engcom-team magento-engcom-team removed the Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed label Jan 12, 2019
@magento-engcom-team
Copy link
Contributor

@saphaljha Thank you for verifying the issue.

Unfortunately, not enough information was provided to created internal ticket. Please consider adding the following:

  • Add "Reproduced on " label(s) to this ticket based on verification result

Once all required information is added, please add label "Issue: Confirmed" again.
Thanks!

@saphaljha saphaljha added Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed labels Jan 12, 2019
@magento-engcom-team
Copy link
Contributor

@saphaljha Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-97604 were created

@magento-engcom-team magento-engcom-team added the Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development label Jan 12, 2019
@saphaljha saphaljha changed the title Admin - dropdown arrow not working on closing Admin - dropdown toggle arrow not working on closing Jan 12, 2019
@niravkrish niravkrish mentioned this issue Jan 12, 2019
Merged
4 tasks
@saphaljha saphaljha added the Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release label Jan 12, 2019
@shikhamis11 shikhamis11 removed their assignment Jan 16, 2019
@magento-engcom-team
Copy link
Contributor

Hi @saphaljha. Thank you for your report.
The issue has been fixed in #20241 by @niravkrish in 2.3-develop branch
Related commit(s):

The fix will be available with the upcoming 2.3.1 release.

@magento-engcom-team magento-engcom-team added the Fixed in 2.3.x The issue has been fixed in 2.3 release line label Jan 19, 2019
magento-engcom-team added a commit that referenced this issue Jan 19, 2019
@magento-engcom-team
ENGCOM-3842: Fixed - Admin - dropdown toggle arrow not working on clo…
5d8498f 
…sing #20240 #20241

 - Merge Pull Request #20241 from niravkrish/magento2:patch-20240
 - Merged commits:
   1. 52130ac
   2. c1d987b
   3. 75d3b00
   4. 860e4e3
magento-engcom-team pushed a commit that referenced this issue Jan 19, 2019
@sivaschenko
ENGCOM-3842: Fixed - Admin - dropdown toggle arrow not working on clo…
8d27ac3 
…sing #20240 #20241
@niravkrish niravkrish mentioned this issue Jan 20, 2019
Merged
4 tasks
niravkrish added a commit to niravkrish/magento2 that referenced this issue Jan 25, 2019
@niravkrish
Merge pull request #6 from niravkrish/2.2-develop-PR-port-20241
0c8e455 
[Backport] Fixed - Admin - dropdown toggle arrow not working on closing magento#20240
@niravkrish niravkrish mentioned this issue Jan 25, 2019
Merged
4 tasks
@saphaljha saphaljha removed their assignment Jan 27, 2019
@magento-engcom-team magento-engcom-team added the Fixed in 2.2.x The issue has been fixed in 2.2 release line label Feb 13, 2019
@magento-engcom-team
Copy link
Contributor

Hi @saphaljha. Thank you for your report.
The issue has been fixed in #20616 by @niravkrish in 2.2-develop branch
Related commit(s):

The fix will be available with the upcoming 2.2.9 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@niravkrish niravkrish

Labels
Component: Ui Fixed in 2.2.x The issue has been fixed in 2.2 release line Fixed in 2.3.x The issue has been fixed in 2.3 release line Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@saphaljha @shikhamis11 @magento-engcom-team @niravkrish