Perhaps this could also work in reverse? Meaning that if a non-dev takes a look at a Jira entry and thinks that they know how they’d approach it they could first make a post in Jira to get feedback from the devs. That way they’d either get some encouragement and direction or preemptive guidance that they’re barking up the wrong tree before they actually start working on the issue.
One thing that the main developers could to do that might help bring people along is to post comments on Jira suggesting where the problem code is likely to be found with hints about what needs to change, then wait a while before fixing the problem (for non-critical bugs).
This is an excellent suggestion. I will do this this next week. Thanks BobRay.
One thing that the main developers could to do that might help bring people along is to post comments on Jira suggesting where the problem code is likely to be found with hints about what needs to change, then wait a while before fixing the problem (for non-critical bugs).
One thing that the main developers could to do that might help bring people along is to post comments on Jira suggesting where the problem code is likely to be found with hints about what needs to change, then wait a while before fixing the problem (for non-critical bugs).
Perhaps this could also work in reverse? Meaning that if a non-dev takes a look at a Jira entry and thinks that they know how they’d approach it they could first make a post in Jira to get feedback from the devs. That way they’d either get some encouragement and direction or preemptive guidance that they’re barking up the wrong tree before they actually start working on the issue.
The advantage of this would be that the onus wouldn’t be on the devs to post tips and info for every post, but only reply to the ones that someone has expressed an interest in working on (although the two methods are not mutually exclusive).