# Issue tickets should not be unconditionally closed automatically due to inactivity
**URL:** https://discuss.bitrise.io/t/issue-tickets-should-not-be-unconditionally-closed-automatically-due-to-inactivity/13223
**Category:** Other Issues
**Created:** [June 5, 2020, 10:57am UTC](https://discuss.bitrise.io/t/issue-tickets-should-not-be-unconditionally-closed-automatically-due-to-inactivity/13223 "2020-06-05T10:57:35Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@koral](https://discuss.bitrise.io/u/koral)
#### Post date: [June 5, 2020, 10:57am UTC](https://discuss.bitrise.io/t/issue-tickets-should-not-be-unconditionally-closed-automatically-due-to-inactivity/13223/1 "2020-06-05T10:57:36Z")
Some issue tickets are closed despite that they are unresolved. For example this one:
> [@File already exists error when building aab](http://discuss.bitrise.io/t/file-already-exists-error-when-building-aab/9983/):
>
> Bitrise Build Issue Report template Description of the issue Bitrise is uploading two .aab files to deploy directory e[34;1mMove APK and AAB files...e[0m copy app/build/intermediates/intermediary\_bundle/release/app-release.aab to /bitrise/deploy/app-release.aab e[33;1m 1 attempt failed:e[0m file already exists at: /bitrise/deploy/app-release.aab e[33;1m Retrying...e[0m copy app/build/outputs/bundle/release/app-release.aab to /bitrise/deploy/app-release20190815132132.aab e[32;1mThe app path …
which has been recently bumped as: [Step duplicates artifact files · Issue #72 · bitrise-steplib/steps-gradle-runner · GitHub](https://github.com/bitrise-steplib/steps-gradle-runner/issues/72)
They should be perhaps closed only manually after explicitly marking as resolved or maybe automatically due to inactivity of reporter asked for additional data. Not just due to Bitrise staff inactivity.
---
### Author:  [@non-binary](https://discuss.bitrise.io/u/non-binary)
#### Post date: [June 5, 2020, 11:40am UTC](https://discuss.bitrise.io/t/issue-tickets-should-not-be-unconditionally-closed-automatically-due-to-inactivity/13223/2 "2020-06-05T11:40:10Z")
Hi @koral,
The Bitrise community forum is primarily for the community to help each other. It is not a main method of accessing support for Bitrise, which is why some tickets go unanswered.
I highly recommend you creating a GH issue for bugs and those types of issues and a support ticket through for all other requests: [https://www.bitrise.io/bitrise-support](https://www.bitrise.io/bitrise-support).
Thanks,
Luna
---
### Author:  [@koral](https://discuss.bitrise.io/u/koral)
#### Post date: [June 5, 2020, 12:00pm UTC](https://discuss.bitrise.io/t/issue-tickets-should-not-be-unconditionally-closed-automatically-due-to-inactivity/13223/3 "2020-06-05T12:00:24Z")
So IMHO especially, automatic ticket close should not happen, maybe disable it at all?
---
### Author:  [@non-binary](https://discuss.bitrise.io/u/non-binary)
#### Post date: [June 10, 2020, 4:39pm UTC](https://discuss.bitrise.io/t/issue-tickets-should-not-be-unconditionally-closed-automatically-due-to-inactivity/13223/4 "2020-06-10T16:39:45Z")
Hi @koral,
I will bring this up at the next team meeting.
---
### Author:  [@system](https://discuss.bitrise.io/u/system)
#### Post date: [July 10, 2020, 4:39pm UTC](https://discuss.bitrise.io/t/issue-tickets-should-not-be-unconditionally-closed-automatically-due-to-inactivity/13223/5 "2020-07-10T16:39:45Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.