Page MenuHomePhabricator

Fix an issue where "Import Columns" could fail on a board for a project with milestones
ClosedPublic

Authored by epriestley on Jan 16 2019, 2:39 PM.
Tags
None
Referenced Files
F15417837: D19978.id47716.diff
Thu, Mar 20, 6:57 PM
Unknown Object (File)
Feb 9 2025, 6:55 AM
Unknown Object (File)
Feb 1 2025, 1:30 PM
Unknown Object (File)
Jan 31 2025, 5:55 PM
Unknown Object (File)
Jan 25 2025, 3:11 AM
Unknown Object (File)
Jan 23 2025, 1:37 AM
Unknown Object (File)
Jan 17 2025, 11:32 PM
Unknown Object (File)
Jan 11 2025, 3:30 PM
Subscribers
None

Details

Summary

See PHI1025. When you "Import Columns", we test if you're trying to import into a board that already has columns. However, this test is too broad (it incorrectly detects "proxy" columns for milestones as columns) and not user-friendly (it returns 400 instead of a readable error).

Correct these issues, and refine some of the logic around proxy columns.

Test Plan
  • Created a project, A.
  • Created a milestone under that project.
  • Imported another project's columns to A's workboard.
    • Before change: Unhelpful 400.
    • After change: import worked fine.
  • Also, hit the new error dialogs and read through them.

Diff Detail

Repository
rP Phabricator
Branch
board1
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 21533
Build 29347: Run Core Tests
Build 29346: arc lint + arc unit

Event Timeline

amckinley added inline comments.
src/applications/project/controller/PhabricatorProjectBoardImportController.php
57

"Source Workboard Has No Columns", if I understand this right.

This revision is now accepted and ready to land.Jan 17 2019, 12:03 AM
src/applications/project/controller/PhabricatorProjectBoardImportController.php
57

Ah, yeah, I think your phrasing is more clear. You just "targeted" this workboard by typing in the name, but it's not really self-evident whether "target" means "source" or "destination".

  • Use "Source" over "Target".
This revision was automatically updated to reflect the committed changes.