Crosslink object if mentioned somewhere
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	hwinkel
	Oct 30 2013, 9:07 PM

Description

seems fabricator user often uses the special syntax to reference objects like T603 or users line @hwinkel. the markup renders the links already quite good.

It would be great to have this links bidirectional, if somebody mention a user the user could have a notification, if somebody have mentioned a Object like Task T603 or Revision this could me added as a kind of comment or reference in the corresponding object.

This way even links in text would be liked and not only explicit dependencies ?!?

{F166117,size=full}

Revisions and Commits

rP Phabricator
	D10451	rPc75495e63fa0 Transactions - add infrastructure for "mentions"

Related Objects

Mentioned In: T6401: Tasks have "citation lists" which link back to all of their references in other parts of Phabricator
T5132: Document the special syntax you can use in commit messages to cause effects
T6059: Prevent objects from mentioning themselves
T4036: Crosslink object if mentioned somewhere
T6058: test task please ignore
Mentioned Here: rPbee1e09fd130: Remove getPHID() from PhabricatorMentionableInterface
rPc75495e63fa0: Transactions - add infrastructure for "mentions"
T4036: Crosslink object if mentioned somewhere

Event Timeline

hwinkel created this task.Oct 30 2013, 9:07 PM

hwinkel raised the priority of this task from to Needs Triage.

hwinkel updated the task description. (Show Details)

hwinkel added a subscriber: hwinkel.

hwinkel added a subscriber: tolbrino.Oct 30 2013, 9:09 PM

hwinkel added a project: Phabricator.Nov 30 2013, 10:14 PM

hwinkel updated the task description. (Show Details)Dec 4 2013, 5:37 AM

hwinkel added a subscriber: hsychla.

This interacts with all the ref/closes/fixes stuff -- generally, I want to add an object-mention edge. We need this for some other stuff too.

carl added a subscriber: carl.Mar 13 2014, 11:44 PM

I'm planning to implement this relatively soon, as the ref/closes/fixes stuff is mostly done. There are basically two open questions:

What does this look like when you look at a mentioned object? If we just dump the mention into the transaction record, it will tend to make things noisier, and I feel like we're leaning heavy on the amount of fluff in transaction records right now. Just dumping it in is easiest by far, though, and maybe it'll be fine.
From a technical perspective, the way edge editing works is weird and backwards, and predates TransactionEditors. It would be good for this to at least move us toward a workable implementation for the other edge relationships (Fixes/Closes, Depends On, etc). I need to think about this a bit and come up with something which gives us a pathway forward.

@carl and I talked about activating it for commits to tracked-but-not-autoclose branches in particular, which seems reasonable to me.

◀ Merged tasks: T5360.

qgil added a subscriber: qgil.Jun 13 2014, 5:07 PM

chad updated the task description. (Show Details)Jun 13 2014, 5:15 PM

chad renamed this task from crosslink object if mentioned somewhere to Crosslink object if mentioned somewhere.Jun 13 2014, 5:20 PM

chad added a project: Transactions.

What about

$someone mentioned this $currentobject in $objectwithmention

e.g.

chad mentioned this task in {T5074: Add `setDisabled(true)` to PHUIPinboardItemView}

hwinkel added a subscriber: thz.Jul 1 2014, 7:35 PM

swisspol added a subscriber: swisspol.Jul 11 2014, 3:29 AM

In ApplicationTransactionEditor, we currently extract all mentioned objects from transactions (in expandRemarkupBlockTransactions()) and then filter out everything that's not a project.
Add some new code to load all the mentioned objects and check which ones implement a new PhabricatorMentionableInterface.
Write a new edge type (e.g., OBJECT_MENTIONS_OBJECT / OBJECT_MENTIONED_BY_OBJECT) against all these objects.
Let's hide this story in the mentioning object and not generate feed stories, email, or notifications for it for now? So the mentioned object just gets a epriestley mentioned this in D123: blah blah transaction with no fanfare.
Implement MentionableInterface on some objects, but not Users, Projects, or Files (since these already have other behaviors).
It would also be nice to not write this edge if we're writing a Ref/Fixes edge. That is, for comment text Fixes T123, it would be nice to interpret that as not being a mention. You might have to add some getPHIDsWhichShallNotBeMentioned($xaction) to support that.

Macro yaaay:

Kind of a silly question but where should MentionableInterface live? I was thinking about making a new application mentions, except there's nothing in there except the interface folder.

This is a good idea I think if we figure we'll ever have a "mentions" application - which is presumably just stats about what was mentioned, maybe a mention feed, and generally not that much utility. So I am not sure if we'll have a Mentions application. :/

The best alternative I can think of is in the "transactions" application.