# Jira Issue Curation

**URL:** <https://talk.openmrs.org/t/jira-issue-curation/29113>\
**Category:** Development\
**Tags:** jira\
**Created:** [June 22, 2020, 4:08pm UTC](https://talk.openmrs.org/t/jira-issue-curation/29113 "2020-06-22T16:08:27Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![ibacher](https://talk.openmrs.org/user_avatar/talk.openmrs.org/ibacher/32/19751_2.png) [@ibacher](https://talk.openmrs.org/u/ibacher)\
**Post date:** [June 26, 2020, 4:41pm UTC](https://talk.openmrs.org/t/jira-issue-curation/29113/15 "2020-06-26T16:41:43Z")

</div>

Here are some of the things I would like to know from a pilot:

- Can we successfully handle both issues being added to the issue queue while maintaining a reasonable view of issue priority?
- What is the best practice for ensuring that issues have been properly evaluated _before_ someone starts working on them?
- How do we deal with issues which end up requiring touching two different code repositories?
- What’s the best practice for dealing with issues reported against the wrong repository?

---

_[View the full topic](https://talk.openmrs.org/t/jira-issue-curation/29113)._