{% extends "issues/base.html" %}
{% load static %}

{% block tab_content %}
<h1 class="text-2xl font-bold text-ellipsis whitespace-nowrap overflow-hidden">Issue Grouping:</h1>

{% comment %}
This template/tab may seem like very little info for a full tab, and that's probably correct. However:

* We need _something_ that's tied to the issue rather than the event, because that's where the .grouping_set().all() lives.
    (yes manual merging isn't implemented in the UI yet, but we follow the datamodel here)

* Better grouping is probably inevitable in the future, at which point this place will be the place

{% endcomment %}

<div class="mt-2 text-slate-700 dark:text-slate-300">Automatic grouping keys attached to this issue.</div>
<ol class="mt-4 space-y-4">
{% for grouper in groupers %}
<li class="border-t border-slate-200 dark:border-slate-700 pt-4 first:border-t-0 first:pt-0">
    <div class="text-sm font-bold text-slate-500 dark:text-slate-400 mb-1">{{ grouper.get_grouping_mechanism_display }}</div>
    <div class="font-mono text-sm break-all leading-relaxed">{{ grouper.grouping_key }}</div>
</li>
{% endfor %}
</ol>
{% endblock %}