We may have different ideas of what is redundant. I'd say that the helper is mainly cleaner because it removed redundancy - but probably at a different level then what you refer to.
I understand that it can be a pain to hunt down helpers. But I think this is the problem that should be solved instead of putting lot's of ruby code in the view. I see two ways of doing this: 
* Canonical helpers. I'd look for these functions in `help/app/helpers/tickets_helper.rb`. It's included in all ticket views and that's where you might want to (re)use these things anyway.
* Explicit helper objects. Helpers are odd because they behave like global functions in the views. They clutter the namespace and you can't tell where they are from. So how about this:

```haml
- ticket = TicketPresenter.new(@ticket)
-# ...
%div
  = t(:regarding_account)
  = ticket.regarding_user_link
```

This way you can easily tell where `regarding_user_link` is defined and the TicketPresenter is a plain ruby class so you can delegate to `@ticket`, include modules and all that jazz.
Draper creates a decorator class to sit next to the views for this. Others like github are using similar approaches: http://warpspire.com/posts/mustache-style-erb/