What do you consider the minimum quality metrics that an Agile team need to have?

[Jerrell Arreza]

Maybe that minimum can be included in JIRA as additional feature especially that there's the perception still in companies with deep-rooted waterfall-ish processes that Agile doesn't have good quality metrics.

[Ivar]

What is "minimum quality metric's"? One or several magic numbers? 

In agile, a user story should have acceptance criteria set forth by the business (product owner). These acceptance criteria together with the user story itself, is collaborated on with the entire team to make sure it is explicit enough to develop, and explicit enough to test. If the business is happy with the acceptance criteria per story, one metric could be that a story passes on all the acceptance criteria. 

Going "down", e.g. towards the code, you can always start setting metrics for the different components - e.g. database-related code should have a 100 % test coverage; code managing external integration's should have 75 % coverage if they are difficult to mock. Of course, all unit tests should be green (e.g. 100 % correct). Remember that 100 % unit test coverage or green result doesn't say anything about the quality of the code - only that you will have a good shot of identifying breaking changes when someone changes the code in the future. 

I guess we can go on and one, but I need a bit more "meat" to work with