# openEHR Specification Problem Report issue tracker

**URL:** <https://discourse.openehr.org/t/openehr-specification-problem-report-issue-tracker/13269>\
**Category:** Technical (archive)\
**Created:** [30 April 2009 23:51 UTC](https://discourse.openehr.org/t/openehr-specification-problem-report-issue-tracker/13269 "2009-04-30T23:51:56Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![thomas.beale](https://discourse.openehr.org/user_avatar/discourse.openehr.org/thomas.beale/32/35_2.png) [@thomas.beale](https://discourse.openehr.org/u/thomas.beale)\
**Post date:** [30 April 2009 23:51 UTC](https://discourse.openehr.org/t/openehr-specification-problem-report-issue-tracker/13269/1 "2009-04-30T23:51:56Z")

</div>

In a recent post I mentioned that we would create a new public Problem Report  
(PR) tracker on openEHR.org for the purpose of raising issues on the  
specifications.

This has now been done - see [http://www.openehr.org/issues/browse/SPECPR](http://www.openehr.org/issues/browse/SPECPR)

A number of existing PRs from the existing SPEC Jira project have been moved  
to this tracker. In future, the SPECPR project will be restricted to CRs  
(change requests) of work actually done on the specifications.

The permissions scheme in Jira can be rather tricky, so I expect we will have  
a few teething problems. However, the intention is that:  
\* the SPECPR tracker is completely open for raising issues  
\* the SPEC tracker is open only to a small number of people who work directly  
on the specifications as a result of community PRs, analysis, discussions etc.

Feel free to browse both the SPEC and SPECPR tracker; if you have an issue  
with the specifications, please look at what has been raised already, and if  
it is a new issue, then raise in SPECPR.

Please report any permissions problems or other problems on this list.

- thomas beale