Should all agile epics be titled in sentences

Question

I'm reorganizing my agile board on youtrack and am trying to conform to the industry best practices however I would much rather call an epic

"User Profile"

as opposed to

"A users can view their own and other users information and content on their user profile"

if I can get away with it.

I'm going to be applying for jobs soon so theres a chance someone might look at what I've done and I just want to make sure I don't look bad because of something like this.

To further clarify how I view each "Type" of issue (to make sure I'm understanding them correctly)

Epic - User Profile (brief description)

Feature - User Feed (detailed description)

Task - A user may like items in the feed

Answer 1

An epic's title should be 'suited for purpose.' It relies on how you use them to determine what that goal is.

Consider the case where you were the only one who knew about the epics. In that case, you should choose an epic title that makes sense to you. If, on the other hand, the epic was to be seen by a large number of business users, it would make sense to use an epic title that meant the most to them.

Because agile methodologies differ so much, there isn't truly a 'best practise' when it comes to this. It's really just a matter of finding a solution that works for your company and, if it doesn't, tweaking it to make it better.