• We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      It would be great to be able to tag any commit within the stash interface

            [BSERV-3999] Create tags directly from stash

            Nevermind. I was confused because admin page said "The Tag Maker" add-on was incompatible and disabled, but it was actually active in my Bitbucket 4.7.1 installation, and I confused it with your implementation. (I should probably file a bug!) The tags UI that you've done is very minimal and nice. Thank you.

            If you really wanted to hammer home the distinction between annotated and non-annotated, one idea would be to dynamically adjust the submit button so that it toggles between <Create Tag> and <Create Annotated Tag> based on whether the "description" box has any content or not. That could help users understand what's going on a little more deeply.

            (Frankly the whole "annotated" vs. "lightweight" tag thing in Git is a pointless distraction and a design flaw from a usability point of view, but it is what it is, and we have to live with it.)

            Julius Davies [bit-booster.com] added a comment - Nevermind. I was confused because admin page said "The Tag Maker" add-on was incompatible and disabled, but it was actually active in my Bitbucket 4.7.1 installation, and I confused it with your implementation. (I should probably file a bug!) The tags UI that you've done is very minimal and nice. Thank you. If you really wanted to hammer home the distinction between annotated and non-annotated, one idea would be to dynamically adjust the submit button so that it toggles between <Create Tag> and <Create Annotated Tag> based on whether the "description" box has any content or not. That could help users understand what's going on a little more deeply. (Frankly the whole "annotated" vs. "lightweight" tag thing in Git is a pointless distraction and a design flaw from a usability point of view, but it is what it is, and we have to live with it.)

            g.sylvie.davies1687549270
            I am from the design team on Bitbucket Server, could you expand on why specifically a checkbox? The current behaviour of creating a tag is that if you type anything into the description, it will automatically become an annotated tag.

            Sam Roberts (Inactive) added a comment - g.sylvie.davies1687549270 I am from the design team on Bitbucket Server, could you expand on why specifically a checkbox? The current behaviour of creating a tag is that if you type anything into the description, it will automatically become an annotated tag.

            A checkbox to toggle whether tag is annotated or not would be nice.

            Julius Davies [bit-booster.com] added a comment - A checkbox to toggle whether tag is annotated or not would be nice.

            Lucy added a comment -

            Bitbucket Server 4.7.1 has been released today and allows users to create and delete tags: https://confluence.atlassian.com/display/BitbucketServer/Bitbucket+Server+4.7+release+notes

            Lucy added a comment - Bitbucket Server 4.7.1 has been released today and allows users to create and delete tags: https://confluence.atlassian.com/display/BitbucketServer/Bitbucket+Server+4.7+release+notes

            +1

            +1

            +1

            ivoecpereira added a comment - +1

            +1

            +1

            Neil added a comment -

            Yes please! I like to do this for release branches, once the release is complete and stable.

            Neil added a comment - Yes please! I like to do this for release branches, once the release is complete and stable.

              lbain Lucy
              brett.murphy Brett Murphy
              Votes:
              324 Vote for this issue
              Watchers:
              161 Start watching this issue

                Created:
                Updated:
                Resolved: