Hi,
If you think the problem is too much information to end-users, How about
using label and filter in JIRA? If you're willing to manage some issues
from JIRA to Trello manually, I think it's easy for you to managing labels
and filters for end-users. And then, if you or someone shares that
Huge +1 to leveraging JIRA functionality here. Conveging
contributors to the ASF projects web presence is usually
very helpful.
If you guys need any help with JIRA -- please let me know.
Thanks,
Roman.
On Sat, Jul 25, 2015 at 6:19 PM, moon soo Lee m...@apache.org wrote:
Thanks Marko Galesic
Thanks Marko Galesic for explanation what you think.
Now, my understanding is, issues are created only from JIRA, and votes are
transferred from Trello to JIRA.
I agree on make end-user participation more easy.
However, synchronizing two different issue tracker sounds very easy to be
error prone
Hi,
I think we need more discussion on it. I'm not really convinced to use two
separate issue tracker.
In my understanding, problem is,
* JIRA is not friendly to non-developers.
Solution proposed from Marko Galesic is,
* Let user create issue on Trello, which has friendly UI for non-developers.
I'm a bit skeptical about duplicating tickets in JIRA Trello for some
reasons
1 Single Point Of Failure.
As you said yourself: My plan is to check JIRA weekly and only take what
in my opinion are mid to high level features within Zeppelin and then, yes, *I
would manually add those cards to
Hi moon,
- Let user create issue on Trello, which has friendly UI for
non-developers.
No, Trello would only reflect issues created in JIRA. Users could go through
JIRA or the mailing list to have new tickets created.
- And create issue on JIRA based on vote on Trello.
Hi moon,
I see your point that there would be overhead in managing two systems. However,
I don’t believe that working within JIRA will achieve what I’m thinking of. I’m
impressed there are people who use JIRA and seem to be end users; however, I
speculate that these are advanced users – edging
Hi guys!
I find the suggestion to vote via trello totally cool and would support it.
So if everyone is OK with this, let's do this.
I was looking for such a possibility to have a community process to
prioritize something for quite some time (have also played with various
JIRA workarounds) - but
Guys,
thank you for great suggestions!
Am I right that you suggest using Trello not instead of ASF hosted
JIRA, but together with it, and are volunteering to support it as a
tool for prioritizing user's feedback?
Also, how do you think, should we then move further discussion to the
Hi all,
I'm wondering if people involved with this project would be willing to maintain
a Trello board for user feature requests. I'd be willing to maintain it,
however I'd like to know that others in the community would market it to those
who would use it (users). I'll be sending this to my
10 matches
Mail list logo
