It's hard to teach people Holacracy. One barrier to understanding is wrapping your head around a bunch of new vocab. If a new word like "tension" adds some nuance not present in a common word, then it's an important thing to keep; if it adds nothing but another word to learn, it's better to stick with a more common word.
I'm wondering if "tension" really adds any nuance, over "issue." I've experimented in my explanations and in actual use in my organization (Snowdrift.coop) and have not noticed any lack of clarity. What are your opinions?
If people have reasons why using "tension" is important, I'll either agree with you and return to using it, or I'll argue why I don't think that reason is actually that important.
I'll head off two reasons that I expect to see pop up: "tension" has a neutral connotation where "issue" has a negative one. I think that "tension" actually is slightly negative, as in, "you could feel the tension in the air", and "issue" is not very much more negative, since it's also used to mean "topic", or a particular release of a publication. Also, in places like github, "issues" covers both bug reports and enhancements -- both directions of "a gap between how things could be and how they are."