Page MenuHomePhabricator

cos (Cosmos Nicolaou)
User

Projects

User does not belong to any projects.

Today

  • Clear sailing ahead.

Tomorrow

  • Clear sailing ahead.

Saturday

  • Clear sailing ahead.

User Details

User Since
May 15 2016, 3:12 AM (256 w, 4 d)
Availability
Available

Recent Activity

Dec 12 2017

spawnlt awarded T12314: Support formal task subtypes (like "bug" vs "feature") a Party Time token.
Dec 12 2017, 10:26 AM · EditEngine, Maniphest, Custom Fields, Feature Request
spawnlt awarded T12588: create subtask side menu to allow creation of subtasks of different types to the parent task a Party Time token.
Dec 12 2017, 10:20 AM · Feature Request

Jul 12 2017

saga.karlsson awarded T12588: create subtask side menu to allow creation of subtasks of different types to the parent task a Love token.
Jul 12 2017, 1:30 PM · Feature Request

May 4 2017

cos added a comment to T12669: differential.revision.search doesn't return the reviewers..

thanks - I'll upgrade!

May 4 2017, 4:21 PM · Bug Report
cos created T12669: differential.revision.search doesn't return the reviewers..
May 4 2017, 2:54 PM · Bug Report
cos added a comment to T12588: create subtask side menu to allow creation of subtasks of different types to the parent task.

thanks - we'll give this a go. It's not clear how often people will need to use this so I agree with your concern about UI clutter.

May 4 2017, 2:47 PM · Feature Request

Apr 24 2017

benwick awarded T12314: Support formal task subtypes (like "bug" vs "feature") a Like token.
Apr 24 2017, 6:44 AM · EditEngine, Maniphest, Custom Fields, Feature Request

Apr 18 2017

cos created T12588: create subtask side menu to allow creation of subtasks of different types to the parent task.
Apr 18 2017, 7:59 PM · Feature Request

Apr 12 2017

cos added a comment to T12535: Diffusion view to show the commits within a range..

this will work just fine, thanks!

Apr 12 2017, 8:27 PM · Feature Request

Apr 11 2017

cos created T12537: Ambiguous display of commits in maniphest.
Apr 11 2017, 5:14 PM · Feature Request
cos created T12535: Diffusion view to show the commits within a range..
Apr 11 2017, 5:05 PM · Feature Request

Apr 4 2017

cos added a comment to T12481: Obtain a link to harbormaster build output from a commit or review..

thanks, this worked for me!

Apr 4 2017, 12:22 AM · Feature Request

Apr 3 2017

cos added a comment to T12481: Obtain a link to harbormaster build output from a commit or review..

thanks, I didn't think to use containerPHIDs, I'll give this a go this coming week and let you know if it works for me. Thanks!

Apr 3 2017, 3:01 AM · Feature Request

Mar 30 2017

cos added a comment to T12314: Support formal task subtypes (like "bug" vs "feature").

ok, that was the problem - default values will cause a field to show up in the 'details' section, thanks!

Mar 30 2017, 8:07 PM · EditEngine, Maniphest, Custom Fields, Feature Request
cos created T12481: Obtain a link to harbormaster build output from a commit or review..
Mar 30 2017, 7:41 PM · Feature Request
cos created T12480: Be able to obtain the commits (related objects) associated with a task and the reviews associated with a commit.
Mar 30 2017, 7:36 PM · Feature Request
cos added a comment to T12314: Support formal task subtypes (like "bug" vs "feature").

ok, so the intent is that any initialized field shows up in details, but no others? If so, then do fields with default values show-up? I have a software version field for example has a default of 0.0.0 and it shows up for subtypes for which it's hidden. Here are some screenshots to show you:

Mar 30 2017, 4:41 PM · EditEngine, Maniphest, Custom Fields, Feature Request
cos added a comment to T12461: more consistency between results of maniphest.query and .search.

We currently display the description in the reports we generate and those reports are themselves markdown, our tools currently upload these docs to phriction.

Mar 30 2017, 4:35 PM · Feature Request

Mar 28 2017

cos added a comment to T12314: Support formal task subtypes (like "bug" vs "feature").

I'm now using this and it works well! I've noticed one wrinkle that I don't understand, namely, the 'Details' section when viewing a task includes some custom fields and not others? In particular, it includes custom fields that are hidden for the current task subtype. Is there anyway of controlling what appears here?

Mar 28 2017, 11:39 PM · EditEngine, Maniphest, Custom Fields, Feature Request
cos created T12461: more consistency between results of maniphest.query and .search.
Mar 28 2017, 11:28 PM · Feature Request

Mar 7 2017

fooishbar awarded T12314: Support formal task subtypes (like "bug" vs "feature") a Mountain of Wealth token.
Mar 7 2017, 9:25 AM · EditEngine, Maniphest, Custom Fields, Feature Request

Mar 6 2017

20after4 awarded T12337: Provide conduit access to related tasks and in particular 'mentions' a Mountain of Wealth token.
Mar 6 2017, 12:29 AM · Feature Request

Mar 4 2017

Luke081515.2 awarded T12314: Support formal task subtypes (like "bug" vs "feature") a Love token.
Mar 4 2017, 11:23 AM · EditEngine, Maniphest, Custom Fields, Feature Request

Mar 1 2017

cos added a comment to T12335: Ability to lock a task to prevent further edits.

I can confirm that advisory locking is acceptable. Locking the whole task is preferable, but we can live with comments not being locked. Thanks!

Mar 1 2017, 10:38 PM · Maniphest, Feature Request
cos added a comment to T12337: Provide conduit access to related tasks and in particular 'mentions'.

sure, I'm fine with letting the dust settle after these changes and deciding then. The edge.search approach would be totally fine since I'm writing a custom client, also, the attachment approach would work since our set of related tasks will be small for the foreseeable future.

Mar 1 2017, 10:37 PM · Feature Request
cos created T12337: Provide conduit access to related tasks and in particular 'mentions'.
Mar 1 2017, 4:16 PM · Feature Request
cos added a comment to T12335: Ability to lock a task to prevent further edits.

Q. Common or rare?
A. Common - we'd lock all tasks before a release.
Q. Lock comments? Do you need to lock comments too, or just other types of edits (like status, priority, title, description, etc)?
A. I'm ambivalent about this, if the lock is mandatory then being able to add comments seems reasonable since someone can point out that the task needs to be unlocked for some reason or other.
Q. In particular, could a solution where anyone could unlock the task be acceptable, as long as they had to explicitly unlock it? Or is it a hard regulatory requirement that unlocking requires some sort of administrator/oversight step?
A. Unclear, I'll ask, but it's probably fine since there's also a 'process' that states how people use the system. (And you'd be surprised how much drama there is inside private companies:-) That is, our conventions are formally documented and people expected (and expect) to follow them.
Q. Lock other objects?
A. Possibly, but I've been pushing back on it for things like code reviews by arguing that 'everything is logged and there's an audit trail' so what does a lock by us? Obviously locking git doesn't really make sense and new comments can't hide old ones so I don't see what the problem is. For tasks, I don't feel I can make that argument since people will naturally just look at the current state of the task unlike code reviews where the history is 'in your face' as it were.

Mar 1 2017, 3:54 PM · Maniphest, Feature Request
cos created T12335: Ability to lock a task to prevent further edits.
Mar 1 2017, 5:32 AM · Maniphest, Feature Request

Feb 28 2017

cos added a comment to T12314: Support formal task subtypes (like "bug" vs "feature").

thanks, sounds great!

Feb 28 2017, 8:51 PM · EditEngine, Maniphest, Custom Fields, Feature Request
cos added a comment to T12314: Support formal task subtypes (like "bug" vs "feature").

"Overall, I think this is the model we should continue under, and task subtyping should be implemented in terms of views of a subset of fields."
"In the current model, you choose a task type first, by selecting a "Create" form, not by choosing from a "Type" dropdown within the task. "

Feb 28 2017, 6:56 PM · EditEngine, Maniphest, Custom Fields, Feature Request
20after4 awarded T12314: Support formal task subtypes (like "bug" vs "feature") a Love token.
Feb 28 2017, 1:59 AM · EditEngine, Maniphest, Custom Fields, Feature Request

Feb 24 2017

cos added a comment to T12314: Support formal task subtypes (like "bug" vs "feature").

I think it's fine to disallow changing from one type to another - can that be enforced? And sure, I think the custom form approach would work but I don't see how to configure/use that - can you point me in the right direction? I presume this implies that the underlying fields are the union of those exposed by all of the forms which would be fine.

Feb 24 2017, 10:23 PM · EditEngine, Maniphest, Custom Fields, Feature Request
cos created T12314: Support formal task subtypes (like "bug" vs "feature").
Feb 24 2017, 9:59 PM · EditEngine, Maniphest, Custom Fields, Feature Request

Jan 8 2017

cos added a comment to T12074: conduit API extensions for subprojects and milestones..

I am currently using project.query rather than project.search. I presume the change you suggest for .search would work for query too since my recollection is that project.query also doesn't return milestones. I tried to use .search originally, but noticed that the attachments available were limited and didn't correspond to the documentation (examples mentions projects, subscribers, but then later on only watchers and members are supported) so I was scared off by the 'may change' warning:-) I can switch to using .search if that's the better thing to do - I presume you'd add attachments for the new types of information to be returned?

Jan 8 2017, 2:27 AM · Feature Request

Jan 6 2017

cos created T12074: conduit API extensions for subprojects and milestones..
Jan 6 2017, 5:01 AM · Feature Request

May 15 2016

cos added Q389: ssh setup problem (Answer 379).
May 15 2016, 5:43 PM
cos updated Q389: ssh setup problem from to ssh setup problem.
May 15 2016, 3:14 AM