# Improving how to develop

**URL:** https://discuss.tryton.org/t/improving-how-to-develop/6006
**Category:** Organisation
**Created:** [March 9, 2023, 6:59am UTC](https://discuss.tryton.org/t/improving-how-to-develop/6006 "2023-03-09T06:59:34Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![raimon](https://discuss-cdn.tryton.org/letter_avatar_proxy/v4/letter/r/59ef9b/32.png) [@raimon](https://discuss.tryton.org/u/raimon)
#### Post date: [March 9, 2023, 6:59am UTC](https://discuss.tryton.org/t/improving-how-to-develop/6006/1 "2023-03-09T06:59:34Z")

</div>

After migration to heptapod, I think are missing some [guide lines](https://www.tryton.org/develop) in how develop section.

Our questions are:

- How to create new issue without labels? In case account user has not permissions to add labels, how should they do it? ( [bugs.tryton.org](http://bugs.tryton.org) was an input to add the module name )
- How approve a merge request? In case account user has not “approve” button actived, how should they do it? ([codereview.tryton.org](http://codereview.tryton.org) was LGTM)

Thanks

---

<div class="post-metadata">

### Author: ![pokoli](https://discuss-cdn.tryton.org/user_avatar/discuss.tryton.org/pokoli/32/22_2.png) [@pokoli](https://discuss.tryton.org/u/pokoli)
#### Post date: [March 9, 2023, 7:50am UTC](https://discuss.tryton.org/t/improving-how-to-develop/6006/2 "2023-03-09T07:50:57Z")

</div>

> [@raimon](#):
>
> In case account user has not permissions to add labels, how should they do it?

If you do not have permisions to add them, others will add them for you.

> [@raimon](#):
>
> In case account user has not “approve” button actived, how should they do it? ([codereview.tryton.org](http://codereview.tryton.org) was LGTM)

Just add a comment expressing your feelings about the issue.

---

<div class="post-metadata">

### Author: ![ced](https://discuss-cdn.tryton.org/user_avatar/discuss.tryton.org/ced/32/1237_2.png) [@ced](https://discuss.tryton.org/u/ced)
#### Post date: [March 9, 2023, 9:03am UTC](https://discuss.tryton.org/t/improving-how-to-develop/6006/3 "2023-03-09T09:03:47Z")

</div>

> [@pokoli](#):
>
> Just add a comment expressing your feelings about the issue.

If it is just to say “LGTM” or “NOT LGTM”, there are emoji buttons for that.

---

<div class="post-metadata">

### Author: ![pokoli](https://discuss-cdn.tryton.org/user_avatar/discuss.tryton.org/pokoli/32/22_2.png) [@pokoli](https://discuss.tryton.org/u/pokoli)
#### Post date: [March 9, 2023, 9:19am UTC](https://discuss.tryton.org/t/improving-how-to-develop/6006/4 "2023-03-09T09:19:46Z")

</div>

Of course but I think we should avoid such comments and be more verbose. Emoijis do not provide any valuable information for others to improve.

For example in case of NOT LGTM we should explain the reasons why we do not like the implemenation and add some note about how to improve it.

In case of LGTM, i think its better to explain what the user tested and why it finds it interesing. This allows others to just skip such test and focus on others.

In resume: When leaving a comment, always think how the comment can the other person in the communication.

---

<div class="post-metadata">

### Author: ![pokoli](https://discuss-cdn.tryton.org/user_avatar/discuss.tryton.org/pokoli/32/22_2.png) [@pokoli](https://discuss.tryton.org/u/pokoli)
#### Post date: [March 9, 2023, 2:28pm UTC](https://discuss.tryton.org/t/improving-how-to-develop/6006/5 "2023-03-09T14:28:59Z")

</div>

> [@raimon](#):
>
> How to create new issue without labels?

Just to clarify, to manage labels you need to request access as developer. So if you follow the guide to contribute you will have access to setting them.

---

<div class="post-metadata">

### Author: ![htgoebel](https://discuss-cdn.tryton.org/user_avatar/discuss.tryton.org/htgoebel/32/1256_2.png) [@htgoebel](https://discuss.tryton.org/u/htgoebel)
#### Post date: [March 17, 2023, 6:08pm UTC](https://discuss.tryton.org/t/improving-how-to-develop/6006/6 "2023-03-17T18:08:05Z")

</div>

I propose using the “approve” feature, as this can be used as a basis for automation later.
