We have a project on our local JIRA server that is used for users to log issues with JIRA itself, and we have used this project for creating items that are used as JIRA internal issues. Do those internal issues have to have a status that is "open", or can we mark them as "closed" and not have any side effects? This would mean they wouldnt show up as outstanding issues in our JIRA issue project.
The only difference between Tempo Internal issues and JIRA issues is, that you only need the "work on Issue" permission for the Project. You do not need to have the "Browse Project" permission.
This makes it possible to log work on internal issues, but you are not allowed to view them and they will not show in Filters you create.
If you allow logging on closed Issues (the JIRA default does not allow this) you can have all these issues in "Closed" status and still log work on them.
As we have created the internal issues in the JIRA issue tracking project, we will need the project to have its permissions to be allowed to be browsed, so unless we move the internal issues, that one is off the table, but thanks anyway.
As for the "work on closed issues". Where about is that set? I have done a test and it looks like our JIRA system is allowing us to log work on the closed items. In the time tracking options, it lists...
The number of working hours per day is 7.5. The number of working days per week is 5. Time estimates will be displayed in the following format: hours (e.g. 36.5h) The current default unit for time tracking is minute. Copying of comments to work description is currently enabled. For the users you wish to be able to log work on issues, ensure that they have the Work On Issues permission in the relevant permission scheme.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG