List maniphest tasks

[Grokzen]

Proposed Functionality

Implement phabfive maniphest list

[D0wn10ad]

Hi, my company's phabricator is now with approx 5000+ tasks and this will basically just run... And run. Not sure is this a good idea

[Grokzen]

@D0wn10ad Do you have any ideas on how to make that better? The things we are discussing is to either make it into a pagination solution where you would only get the first page of items and then have to manually or via code choose another page. Possible to include the cursor solution that you started on in your PR.

The other solution would be to base this on time instead of number of tickets. Like you would get only last 30days, but this is less optimal then pagination solution. It gets a bit tricky however because this is run from CLI and not as much from other API:s clients that probably would prefer pagination solution.

[holmboe]

@D0wn10ad we have revised the "search" command and made it vastly more powerful. See

• 🚀 Implement pagination for Maniphest task search API calls #90
• fix(phabfive): All projects weren't fetched properly due to pagination #79
• Support wildcard patterns in project search #72
• 🚨 feat(search): Add negation support for search patterns #91
• 🚀 feat: Add advanced project filtering with AND/OR logic #94
• Board matching should support additional hashtags #102
• 🔧 Refactor: Ensure proper yaml output using yaml libraries to print #92
• feat(maniphest): Add Priority Filtering and Restructure Task Output #83

The only UX shortcoming I can think of right now from and end user perspective is that we have resorted to outputting valid YAML with lots of data for each task and encourage using templating tools such as Jinja2 CLI to bake it into the desired format. See #63 as an example. This will of course be very chatty for scenarios where you don't filter it through Jinja2, yq or similar.

[holmboe]

So, "maniphest list" is not needed when "maniphest search" and "maniphest show" is available. Closing this issue.