Skip to content

Searching through the changeset repository could show which commits are already linked to tickets  #202

@luzpaz

Description

@luzpaz

Scenario: A project is migrating from python2 to python3 and you can imagine it's a ton of commits. Some of the devs are not associating their commits to the designated ticket. So in order to organize and associate all the py3 commits they need to be searched by keywords. Say that be 'py3' so using the search function brings up all commits with py3 in them. Now some of the commits have been associated already with the ticket... but I can't tell which one since the UI doesn't indicate that. So I need to open each an everyone individually in order to ascertain if it's been attached.

Solution: commits that are attached to a ticket can be designated with a certain color or mention highlight the ticket they are attached to somewhere within the search results.

Related to #128

Edit:
Mind you this is also an issue say if not all the commits have the same identifying keyword. Instead of 'py3' what if the commit message has 'python3' in it or 'python 3'. Some of the commits will have multiple keywords..so the results will overlap. Again, there is no way to see what commits have been attached so one needs to open each and everyone of them.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions