[xwiki-commits] r2503 - in xwiki/trunk/web/standard/src/main/webapp/skins: albatross dodo finch

Zeljko Trogrlic zeljko_t at post.htnet.hr
Sat Mar 31 18:58:28 CEST 2007


Vincent Massol wrote:
> The JIRA strategy that we're following is that we need to make is 
> user-oriented. It's for end users. It's not for us, we don't need it, we 
> can look at commit messages to see what's being done, we can look at the 
> source code, etc. JIRA issues are a communication channel with our users 
> and as such they need to clearly show what's changed for them. They 
> don't need (and shouldn't see) things like "remove $tdoc for permission 
> improvement". This is not undestandable for a user. But something like 
> "Allow setting permissions on translated version of documents" (this is 
> a fake example just to make a point).

I agree with you. Before adding new issue, I usually check is it already 
reported, but some of the issues have just non-descriptive subject. 
Documenting everything in JIRA could reduce duplicates and improve 
communication with users (e.g. what's reported, when it will be fixed etc.)





More information about the devs mailing list