# Bug or Feature?

**URL:** <https://gramps.discourse.group/t/bug-or-feature/9555>\
**Category:** Bug triage\
**Created:** [May 27, 2026, 11:30am UTC](https://gramps.discourse.group/t/bug-or-feature/9555 "2026-05-27T11:30:46Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\
**Post date:** [May 27, 2026, 11:30am UTC](https://gramps.discourse.group/t/bug-or-feature/9555/1 "2026-05-27T11:30:46Z")

</div>

Sometimes I waffle about whether an issue should be filed as a bug or as a feature. I will be filing a issue on MantisBT either way. But an issue might be a judgement call. And a non-obvious contributing factor is that a **Feature/Enhancement Request** seems to be overlooked more consistently.

This thread is for bug testers who want help finishing off particular waffles.

---

<div class="post-metadata">

**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\
**Post date:** [May 27, 2026, 11:34am UTC](https://gramps.discourse.group/t/bug-or-feature/9555/2 "2026-05-27T11:34:47Z")

</div>

For example: it might a bug or an enhancement that Gramps utilizes historically deprecated unencrypted `http://` traffic in its constants.

Gramps uses outdated “Not Secure” http:

> <https://github.com/gramps-project/gramps/blob/8d7b4065ae75daba935de08209a30a2fbfe913dc/gramps%2Fgen%2Fconst.py#L62-L66>

Is this a bug or an enhancement?

---

<div class="post-metadata">

**Author:** ![codefarmer](https://avatars.discourse-cdn.com/v4/letter/c/b9e5f3/32.png) [@codefarmer](https://gramps.discourse.group/u/codefarmer)\
**Post date:** [May 27, 2026, 4:01pm UTC](https://gramps.discourse.group/t/bug-or-feature/9555/3 "2026-05-27T16:01:22Z")

</div>

One way to think through whether an issue is a bug or not is to ask whether the behavior observed violates (1) user documentation of expected behavior, (2) development documentation (e.g. specs, GEPS etc.), or (3) expected implemented behavior (code behavior). If yes, I would categorize it a bug. If there’s no expectation some behavior was ever expected via documentation or code, it makes sense to call it a request/wish.