Clean up your issue tracker by using only the most essential attributes for your team. Are you lost in using Jira issue attributes effectively? Do you feel that set up guidelines are not obeyed by the team at all, because teammates have a different understanding of what each attribute really means? When many available attributes are mandated, the team will be overwhelmed, and using attributes is only perceived as bureaucracy without purpose. I worked with Jira for many years and faced exactly this issue. But it's not only about Jira; all issue tracking tools provide a bunch of attributes which can be set on an issue. This article tries to simplify things and gives some useful hints. It collects available attributes and briefly discusses their purpose (or what I think the purpose should be). In the Jira world, the term "field" is used. But I prefer to use the more generic term "attributes". But before that, we must be on the same page about what an "Issue" really means.…