\n\nAnd here is the outcome on BitBucket:\n\u003Cimg width=\"479\" height=\"182\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/11c2a65d-cbf2-4162-9805-3d035bdac04e\" />\n\n\n### Steps to reproduce\n\n1. Run Woodpecker with BitBucket Cloud forge\n2. Create a pipeline that uses a matrix\n3. Let the pipeline finish on Woodpecker\n4. Observe the build statuses on the commit in BitBucket\n\n### Expected behavior\n\nBoth pipelines should show completed.\n\n### System Info\n\n```shell\nWoodpecker version: v3.8.0\n```\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [x] Read the [docs](https://woodpecker-ci.org/docs/intro).\n- [x] Check that there isn't [already an issue](https://github.com/woodpecker-ci/woodpecker/issues) that reports the same bug to avoid creating a duplicate.\n- [x] Checked that the bug isn't fixed in the `next` version already [https://woodpecker-ci.org/versions]",[3069],{"name":3024,"color":3025},5338,"Build status not completing on matrix pipelines with BitBucket","2025-07-17T18:03:12Z","https://github.com/woodpecker-ci/woodpecker/issues/5338",0.77161306,{"description":3076,"labels":3077,"number":3080,"owner":3027,"repository":3028,"state":3081,"title":3082,"updated_at":3083,"url":3084,"score":3085},"### Component\r\n\r\nweb-ui\r\n\r\n### Describe the bug\r\n\r\njust saw this... Open for example https://ci.woodpecker-ci.org/woodpecker-ci/woodpecker/pipeline/6081 and look at the changed files counter\r\n\r\n### System Info\r\n\r\n```shell\r\nour ci\r\n```\r\n\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n\r\n",[3078,3079],{"name":3024,"color":3025},{"name":3039,"color":3040},1843,"closed","Changed files counter shows 0 if opening pipeline directly","2023-10-15T07:14:06Z","https://github.com/woodpecker-ci/woodpecker/issues/1843",0.7113716,{"description":3087,"labels":3088,"number":3090,"owner":3027,"repository":3028,"state":3081,"title":3091,"updated_at":3092,"url":3093,"score":3094},"### Component\n\nweb-ui\n\n### Describe the bug\n\nIn case you try to trigger a manual pipeline that does not start an actual pipeline as all workflows have been filtered and returns 204 we want the UI to show this as a toast and return to the manual pipeline prompt.\n\n### Steps to reproduce\n\n1. create an empty repo\n2. trigger a manual pipeline\n3. receive 204 and see loading spinner forever\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\ncommit: 6161a7413d831dc98c47aff4f7f4a6d175c2ec2f (3.4.0)\n```\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [x] Read the [docs](https://woodpecker-ci.org/docs/intro).\n- [x] Check that there isn't [already an issue](https://github.com/woodpecker-ci/woodpecker/issues) that reports the same bug to avoid creating a duplicate.\n- [x] Checked that the bug isn't fixed in the `next` version already [https://woodpecker-ci.org/versions]",[3089],{"name":3024,"color":3025},4978,"Show pipeline was filtered for manual pipelines","2025-03-18T13:43:52Z","https://github.com/woodpecker-ci/woodpecker/issues/4978",0.72780925,{"description":3096,"labels":3097,"number":3099,"owner":3027,"repository":3028,"state":3081,"title":3100,"updated_at":3101,"url":3102,"score":3103},"### Component\n\nserver\n\n### Describe the bug\n\nWhen a pipeline with multiple workflows starts a correct status is sent at first BitBucket correctly displays that build is in progress. When the build finishes however, only one build is displayed as finished but the other one is still in progress marking the whole commit as in progress(this is internal BitBucket logic). \n\nHere is a pipeline that has two workflows:\n\n\n\nAnd here is the outcome on BitBucket:\n\n\n\nI asked @langecode if he can take a look and we realized that there is a problem in BitBucket forge implementation of `Status` function. It looks like that for each call of `Status` function we send a status of the whole pipeline when we should've sent a status of individual workflows. I.e. change status of https://github.com/woodpecker-ci/woodpecker/blob/main/server/forge/bitbucketdatacenter/bitbucketdatacenter.go#L314\n\nTo:\n```go\nState: convertStatus(workflow.State)\n```\n\n### Steps to reproduce\n\n1. Run woodpecker with BitBucket Datacenter forge\n2. Create a pipeline that has multiple workflows\n3. Let the pipeline finish on woodpecker\n4. Observe the build statuses on the commit in BitBucket\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\nWoodpecker version: v3.5.2\nBitBucket Datacenter version: v8.18.1\n```\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [x] Read the [docs](https://woodpecker-ci.org/docs/intro).\n- [x] Check that there isn't [already an issue](https://github.com/woodpecker-ci/woodpecker/issues) that reports the same bug to avoid creating a duplicate.\n- [x] Checked that the bug isn't fixed in the `next` version already [https://woodpecker-ci.org/versions]",[3098],{"name":3024,"color":3025},5177,"Statuses get incorrectly reported for multi workflow pipelines on BitBucket","2025-05-19T11:01:04Z","https://github.com/woodpecker-ci/woodpecker/issues/5177",0.75439304,{"description":3105,"labels":3106,"number":3114,"owner":3027,"repository":3028,"state":3081,"title":3115,"updated_at":3116,"url":3117,"score":3118},"### Component\n\ncli\n\n### Describe the bug\n\n`woodpecker-cli pipeline logs` is hardly usable and does not comply to the docs.\r\n\r\nThe help text is:\r\n```txt\r\n$ woodpecker-cli pipeline logs help\r\nNAME:\r\n woodpecker-cli pipeline logs - show pipeline logs\r\n\r\nUSAGE:\r\n woodpecker-cli pipeline logs [command options]\u003Crepo-id|repo-full-name> [pipeline] [stepID]\r\n\r\nOPTIONS:\r\n --help, -h show help\r\n```\r\n\r\nstating that `pipeline` and `stedID` are optional, but they are not and there is no hint of how to get the `stepId`\r\n\r\n\r\nI do not know, if this classifies as a bug or feature request\n\n### Steps to reproduce\n\n`165` is the id of one of our repos, 21945 is a pipeline. To reproduce change against the ids of one of your repos / pipelines.\r\n\r\n\r\nOnly with repo:\r\n```bash\r\n$ woodpecker-cli pipeline logs 165\r\n12:01PM FTL error running cli error=\"strconv.ParseInt: parsing \\\"\\\": invalid syntax\"\r\n```\r\n\r\nWith repo and pipeline:\r\n```bash\r\n$ woodpecker-cli pipeline logs 165 21945\r\n12:02PM FTL error running cli error=\"strconv.ParseInt: parsing \\\"\\\": invalid syntax\"\r\n```\r\n\r\nSo let's try it with a step:\r\n\r\n```txt\r\n$ woodpecker-cli pipeline logs 165 21945 1\r\n12:41PM FTL error running cli error=\"client error 404: \"\r\n$ woodpecker-cli pipeline logs 165 21945 2\r\n12:41PM FTL error running cli error=\"client error 400: \"\r\n```\r\n\r\nNote: Two different error codes (404 i can understand, 400 not)\r\n\r\nThe cli doesn't give a clue too:\r\n\r\n```txt\r\n$ woodpecker-cli pipeline ps 165 21945\r\nStep #2\r\nStep: clone\r\nState: success\r\n\r\nStep #3\r\nStep: wartung-weekly\r\nState: failure\r\n\r\nStep #4\r\nStep: Send E-Mail\r\nState: success\r\n``` \r\n\r\nWhat actually works is:\r\n\r\n```bash\r\n$ woodpecker-cli pipeline logs 165 21945 158434\r\n```\r\n\r\nThe `stepID` I got from the browser network window.\r\n\n\n### Expected behavior\n\nI would expect that:\r\n\r\n- parse errors indicate, what went wrong\r\n- `pipeline` is not optional as there is no god default behavior and you can find out about them using `pipeline ls`\r\n- `stepID` is not mandatory. If omitted, you get the complete log of the pipeline\r\n- Error codes are equal for invalid stepID.\r\n- There is a human friendly way of getting the `stepID` maybe added to `pipeline ps` or\r\n or a human friendly way of specifying the `stepID`\r\n\r\nBonus:\r\n- Have a way to get the logs of a single workflow\n\n### System Info\n\n```shell\ncli-version 2.6.0\n```\n\n\n### Additional context\n\nMay be related to #1824\n\n### Validations\n\n- [X] Read the [docs](https://woodpecker-ci.org/docs/intro).\n- [X] Check that there isn't [already an issue](https://github.com/woodpecker-ci/woodpecker/issues) that reports the same bug to avoid creating a duplicate.\n- [X] Checked that the bug isn't fixed in the `next` version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]",[3107,3108,3111],{"name":3024,"color":3025},{"name":3109,"color":3110},"cli","1d76db",{"name":3112,"color":3113},"ux","fef2c0",3911,"woodpecker-cli pipeline logs hardly usabe","2024-07-18T18:39:20Z","https://github.com/woodpecker-ci/woodpecker/issues/3911",0.7553262,{"description":3120,"labels":3121,"number":3125,"owner":3027,"repository":3028,"state":3081,"title":3126,"updated_at":3127,"url":3128,"score":3129},"### Clear and concise description of the problem\n\nIf I have a long list of pipelines and steps and one of them fails, GitHub will present me the link to it. But if I click on that link the woodpecker UI does not take me to that particular pipeline/workflow, I have to scroll down till I find the correct one.\n\n### Suggested solution\n\nscroll the pipeline/workflow into view according to the information given in the URL, similar as done for the log-line number if the URL has a `#L` attached to it\n\n### Alternative\n\n_No response_\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [x] Checked that the feature isn't part of the `next` version already [https://woodpecker-ci.org/versions]\n- [x] Read the [docs](https://woodpecker-ci.org/docs/intro).\n- [x] Check that there isn't already an [issue](https://github.com/woodpecker-ci/woodpecker/issues) that request the same feature to avoid creating a duplicate.",[3122,3123,3124],{"name":3039,"color":3040},{"name":3050,"color":3051},{"name":3112,"color":3113},5081,"scroll to pipeline when navigating through an URL/link","2025-04-18T19:58:47Z","https://github.com/woodpecker-ci/woodpecker/issues/5081",0.76011175,["Reactive",3131],{},["Set"],["ShallowReactive",3134],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fLkIq_oUAtPLYZuOHDSBJR02wpeRogsi89SDVXIBaTVA":-1},"/woodpecker-ci/woodpecker/1583"]