I have created a few tags in my git repository.

      {{

      {\\ $ git tag -l\\ v0.9.10\\ v0.9.11\\ version-0.9.10 $ git status h1. On branch master nothing to commit (working directory clean) $ git push origin\\ Everything up-to-date }

      }}

      But download page ( https://bitbucket.org/afiskon/pl-vkmp3/downloads ) says the following:

      {{{
      Tags

      No tags exist for pl-vkmp3 yet.
      }}}

      Looks like a bug.

            [BCLOUD-3468] BitBucket does not show tags in git repository

            gdahilig added a comment -

            Attachment 1307493220-screenshot.png has been added with description: Originally embedded in Bitbucket issue #3468 in site/master

            gdahilig added a comment - Attachment 1307493220-screenshot.png has been added with description: Originally embedded in Bitbucket issue #3468 in site/master

            gdahilig added a comment -

            Attachment 1104501596-screenshot%202.png has been added with description: Originally embedded in Bitbucket issue #3468 in site/master

            gdahilig added a comment - Attachment 1104501596-screenshot%202.png has been added with description: Originally embedded in Bitbucket issue #3468 in site/master

            Oops, my bad: whether or not tags are pushed is configurable. Apparently the Maven release plugin was pushing the tags to our in-house repositories as part of "mvn release:perform" or prepare. The following seems to make the tags visible on BitBucket:

            #!bash
            
            git push --tags bitbucket
            

            Note that "bitbucket" is the name of the remote I gave to BitBucket, rather than "origin", which was already in use.

            Rob Anderson added a comment - Oops, my bad: whether or not tags are pushed is configurable. Apparently the Maven release plugin was pushing the tags to our in-house repositories as part of "mvn release:perform" or prepare. The following seems to make the tags visible on BitBucket: #!bash git push --tags bitbucket Note that "bitbucket" is the name of the remote I gave to BitBucket, rather than "origin", which was already in use.

            The fig leaf over the naked bug is the BitBucket tag documentation that says that only "annotated" tags work. (made with "git tag -a ..." command or similar).

            Of course, if you use something like the Maven release tool/plugin, it does not create "annotated" tags, just vanilla (no metadata) tags. Which brings me back to how I know about the documentation - I can't see my tags, either.

            The tags feature in BitBucket needs some more work, perhaps a checkbox to toggle annotated or not visibility. Having to drill down into documentation that tells you that most of what is done with tags won't work is not that helpful.

            Rob Anderson added a comment - The fig leaf over the naked bug is the BitBucket tag documentation that says that only "annotated" tags work. (made with "git tag -a ..." command or similar). Of course, if you use something like the Maven release tool/plugin, it does not create "annotated" tags, just vanilla (no metadata) tags. Which brings me back to how I know about the documentation - I can't see my tags, either. The tags feature in BitBucket needs some more work, perhaps a checkbox to toggle annotated or not visibility. Having to drill down into documentation that tells you that most of what is done with tags won't work is not that helpful.

            @detkin, I am curious why this issue is marked as resolved though people report the issue is still there? I have a repo and just created a tag in the web interface but it doesn't show up in the list of tags on Commits page. There's definitely an issue with it. Maybe just caching. But it is a bug from user standpoint.

            Andrew Tabit added a comment - @detkin, I am curious why this issue is marked as resolved though people report the issue is still there? I have a repo and just created a tag in the web interface but it doesn't show up in the list of tags on Commits page. There's definitely an issue with it. Maybe just caching. But it is a bug from user standpoint.

            I have the same problem and logging out-and-in does not work for me. Tag I created from Visual Studio 2015 is not shown in my repository. I do check from Git Bash and can see the tag there. Any comment? I need help.

            serkankalay added a comment - I have the same problem and logging out-and-in does not work for me. Tag I created from Visual Studio 2015 is not shown in my repository. I do check from Git Bash and can see the tag there. Any comment? I need help.

            Same problem here.

            kamran_soomro's solution worked for me. Thanks

            Asim Liaquat added a comment - Same problem here. kamran_soomro's solution worked for me. Thanks

            ads-jyoung added a comment -

            I pushed the tag, and I didn't see the tag in the commits list for about 10 minutes, but I could see it on the commit itself.
            Logout and login didn't seem to accelerate this timeline.
            After waiting, I can now see it in the commits list.

            ads-jyoung added a comment - I pushed the tag, and I didn't see the tag in the commits list for about 10 minutes, but I could see it on the commit itself. Logout and login didn't seem to accelerate this timeline. After waiting, I can now see it in the commits list.

            In my case, logout and login to Bitbucket worked.

            kamran_soomro added a comment - In my case, logout and login to Bitbucket worked.

            Same problem here. We have 2 tags showing in the main UI but the popover says 'No matching tags'

            benreed-careflow added a comment - Same problem here. We have 2 tags showing in the main UI but the popover says 'No matching tags'

              Unassigned Unassigned
              legacy-bitbucket-user Legacy Bitbucket Cloud User (Inactive)
              Affected customers:
              0 This affects my team
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: