# Issues and Branchs

**URL:** <https://forum.gitea.com/t/issues-and-branchs/1452>\
**Category:** Install/Maintain/Configure\
**Created:** [September 5, 2019, 6:26am UTC](https://forum.gitea.com/t/issues-and-branchs/1452 "2019-09-05T06:26:23Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![scandinave](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/scandinave/32/4853_2.png) [@scandinave](https://forum.gitea.com/u/scandinave)\
**Post date:** [September 5, 2019, 6:26am UTC](https://forum.gitea.com/t/issues-and-branchs/1452/1 "2019-09-05T06:26:23Z")

</div>

Is there any reason to not permit the addition of a Branch to an issue after this issue has been created?

i have seen this in the gitea/templates/repo/issue/branch\_selector\_field.tmpl code :

What is the purpose of ReadOnly. I mean I should be able as Dev to create Branch related to an issue created by a customer. My customer does’t know and can’t create the Branch when the issue is created.

---

<div class="post-metadata">

**Author:** ![lunny](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/lunny/32/4701_2.png) [@lunny](https://forum.gitea.com/u/lunny)\
**Post date:** [September 6, 2019, 12:26pm UTC](https://forum.gitea.com/t/issues-and-branchs/1452/2 "2019-09-06T12:26:02Z")

</div>

I think no reason and just need a PR. There is already a similar issue on gitea.

---

<div class="post-metadata">

**Author:** ![scandinave](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/scandinave/32/4853_2.png) [@scandinave](https://forum.gitea.com/u/scandinave)\
**Post date:** [September 6, 2019, 5:11pm UTC](https://forum.gitea.com/t/issues-and-branchs/1452/3 "2019-09-06T17:11:53Z")

</div>

Ok i will try to make a PR. Do you have the issue ID related to this problem?

[Edit] done : [https://github.com/go-gitea/gitea/pull/8119](https://github.com/go-gitea/gitea/pull/8119)
