[AR-1281] Armbian community automated build - Jira

Igor Pecovnik

changed the StatusDecember 17, 2022 at 12:28 PM

In Progress

Done

Igor Pecovnik

updated the ResolutionDecember 17, 2022 at 12:28 PM

None

Done

Igor Pecovnik

updated the Fix versionsDecember 17, 2022 at 12:28 PM

None

23.02

Igor Pecovnik

updated the DescriptionAugust 7, 2022 at 8:38 PM

Last year we concluded to shrink supported board count [https://www.armbian.com/newsflash/armbian-needs-your-help/|https://www.armbian.com/newsflash/armbian-needs-your-help/|smart-link] and stop providing community supported configuration [https://docs.armbian.com/User-Guide_Board-Support-Rules/|https://docs.armbian.com/User-Guide_Board-Support-Rules/|smart-link] . Main idea of this is to make a clean line what is supported and what not. Also an attempt to lower stress from support. But. Images that are in the system and those which are not (yet) are usually produced: * by developers individually * by 3rd party projects: [https://github.com/ophub/amlogic-s9xxx-armbian|https://github.com/ophub/amlogic-s9xxx-armbian|smart-link] * 3rd party Linux distros (manjaro, dietpi, debian, … ) usually just “supports” everything For those working, half or not working images, people are still asking us on our forums for support so we didn’t actually fix much. I didn’t expect and we also shouldn’t drive users away because of this. Just solve this better … This means it makes little sense to not provide images at all so it might be sane to come out with some automated solution that can be used - primarily by us & our community. Working POC exists on: [https://github.com/armbian/community|https://github.com/armbian/community|smart-link] Is a dedicated repository which is holding up to 3 releases of targets that are not end of life (EOL) or supported. For EOL we don’t provide images as they usually don’t build or are just obsolete, while for supported we provide stable downloads from our fast download infrastructure with torrents. This repository contains Actions scripts that builds images from ([beta.armbian.com|http://beta.armbian.com]) nightly repository on every 6 hours. Since we easily hit API rate limits, we have to (automatically) repeat builds to complete one version many times until all images are successfully uploaded. Releases are only uploaded to GitHub and IMO it should stay this way, unless this is a problem for Chinese users? - it is possible to (ready but not enabled) upload to our infrastructure or just somewhere else then GitHub. Each targets gets 2 x CLI and 2 x XFCE desktop images in latest Debian and Ubuntu flavour. If BUILD_DESKTOP=”no” is set in the board config, then desktop images are not generated. Download link: [https://github.com/armbian/community/releases/latest|https://github.com/armbian/community/releases/latest]

Last year we concluded to shrink supported board count [https://www.armbian.com/newsflash/armbian-needs-your-help/|https://www.armbian.com/newsflash/armbian-needs-your-help/|smart-link] and stop providing images for not supported hw [https://docs.armbian.com/User-Guide_Board-Support-Rules/|https://docs.armbian.com/User-Guide_Board-Support-Rules/|smart-link] . Main idea of this is to make a clean line what is supported and what not. Also an attempt to lower stress from support. But. Images that are in the system and those which are not (yet) are usually produced: * by developers individually * by 3rd party projects: [https://github.com/ophub/amlogic-s9xxx-armbian|https://github.com/ophub/amlogic-s9xxx-armbian|smart-link] * 3rd party Linux distros (manjaro, dietpi, debian, … ) usually just “supports” everything For those working, half or not working images, people are still asking us on our forums for support so we didn’t actually fix much. I didn’t expect and we also shouldn’t drive users away because of this. Just solve this better … This means it makes little sense to not provide images at all so it might be sane to come out with some automated solution that can be used - primarily by us & our community. Working POC exists on: [https://github.com/armbian/community|https://github.com/armbian/community|smart-link] Is a dedicated repository which is holding up to 3 releases of targets that are not end of life (EOL) or supported. For EOL we don’t provide images as they usually don’t build or are just obsolete, while for supported we provide stable downloads from our fast download infrastructure with torrents. This repository contains Actions scripts that builds images from ([beta.armbian.com|http://beta.armbian.com]) nightly repository on every 6 hours. Since we easily hit API rate limits, we have to (automatically) repeat builds to complete one version many times until all images are successfully uploaded. Releases are only uploaded to GitHub and IMO it should stay this way, unless this is a problem for Chinese users? - it is possible to (ready but not enabled) upload to our infrastructure or just somewhere else then GitHub. Each targets gets 2 x CLI and 2 x XFCE desktop images in latest Debian and Ubuntu flavour. If BUILD_DESKTOP=”no” is set in the board config, then desktop images are not generated. Download link: [https://github.com/armbian/community/releases/latest|https://github.com/armbian/community/releases/latest]

Igor Pecovnik

updated the DescriptionAugust 7, 2022 at 8:26 PM

Last year we concluded to shrink supported board count [https://www.armbian.com/newsflash/armbian-needs-your-help/|https://www.armbian.com/newsflash/armbian-needs-your-help/|smart-link] and stop providing community supported configuration [https://docs.armbian.com/User-Guide_Board-Support-Rules/|https://docs.armbian.com/User-Guide_Board-Support-Rules/|smart-link] . Main idea of this is to make a clean line what is supported and what not. Also an attempt to lower stress from support. But. Images that are in the system and those which are not (yet) are usually produced: * by developers individually * by 3rd party projects: [https://github.com/ophub/amlogic-s9xxx-armbian|https://github.com/ophub/amlogic-s9xxx-armbian|smart-link] * 3rd party Linux distros (manjaro, dietpi, debian, … ) usually just “supports” everything For those working, half or not working images, people are still asking us on our forums for support so we didn’t actually fix much. This means it makes little sense to not provide images at all so it might be sane to come out with some automated solution that can be used - primarily by us & our community. Working POC exists on: [https://github.com/armbian/community|https://github.com/armbian/community|smart-link] Is a dedicated repository which is holding up to 3 releases of targets that are not end of life (EOL) or supported. For EOL we don’t provide images as they usually don’t build or are just obsolete, while for supported we provide stable downloads from our fast download infrastructure with torrents. This repository contains Actions scripts that builds images from ([beta.armbian.com|http://beta.armbian.com]) nightly repository on every 6 hours. Since we easily hit API rate limits, we have to (automatically) repeat builds to complete one version many times until all images are successfully uploaded. Releases are only uploaded to GitHub and IMO it should stay this way, unless this is a problem for Chinese users? - it is possible to (ready but not enabled) upload to our infrastructure or just somewhere else then GitHub. Each targets gets 2 x CLI and 2 x XFCE desktop images in latest Debian and Ubuntu flavour. If BUILD_DESKTOP=”no” is set in the board config, then desktop images are not generated. Download link: [https://github.com/armbian/community/releases/latest|https://github.com/armbian/community/releases/latest]

Last year we concluded to shrink supported board count [https://www.armbian.com/newsflash/armbian-needs-your-help/|https://www.armbian.com/newsflash/armbian-needs-your-help/|smart-link] and stop providing community supported configuration [https://docs.armbian.com/User-Guide_Board-Support-Rules/|https://docs.armbian.com/User-Guide_Board-Support-Rules/|smart-link] . Main idea of this is to make a clean line what is supported and what not. Also an attempt to lower stress from support. But. Images that are in the system and those which are not (yet) are usually produced: * by developers individually * by 3rd party projects: [https://github.com/ophub/amlogic-s9xxx-armbian|https://github.com/ophub/amlogic-s9xxx-armbian|smart-link] * 3rd party Linux distros (manjaro, dietpi, debian, … ) usually just “supports” everything For those working, half or not working images, people are still asking us on our forums for support so we didn’t actually fix much. I didn’t expect and we also shouldn’t drive users away because of this. Just solve this better … This means it makes little sense to not provide images at all so it might be sane to come out with some automated solution that can be used - primarily by us & our community. Working POC exists on: [https://github.com/armbian/community|https://github.com/armbian/community|smart-link] Is a dedicated repository which is holding up to 3 releases of targets that are not end of life (EOL) or supported. For EOL we don’t provide images as they usually don’t build or are just obsolete, while for supported we provide stable downloads from our fast download infrastructure with torrents. This repository contains Actions scripts that builds images from ([beta.armbian.com|http://beta.armbian.com]) nightly repository on every 6 hours. Since we easily hit API rate limits, we have to (automatically) repeat builds to complete one version many times until all images are successfully uploaded. Releases are only uploaded to GitHub and IMO it should stay this way, unless this is a problem for Chinese users? - it is possible to (ready but not enabled) upload to our infrastructure or just somewhere else then GitHub. Each targets gets 2 x CLI and 2 x XFCE desktop images in latest Debian and Ubuntu flavour. If BUILD_DESKTOP=”no” is set in the board config, then desktop images are not generated. Download link: [https://github.com/armbian/community/releases/latest|https://github.com/armbian/community/releases/latest]

Igor Pecovnik

updated the DescriptionAugust 7, 2022 at 8:21 PM

Last year we concluded to shrink supported board count [https://www.armbian.com/newsflash/armbian-needs-your-help/|https://www.armbian.com/newsflash/armbian-needs-your-help/|smart-link] and stop providing community supported configuration [https://docs.armbian.com/User-Guide_Board-Support-Rules/|https://docs.armbian.com/User-Guide_Board-Support-Rules/|smart-link] . Main idea of this is to make a clean line what is supported and what not. Also an attempt to lower stress from support. But. Images that are in the system and those which are not (yet) are usually produced: * by developers individually * by 3rd party projects: [https://github.com/ophub/amlogic-s9xxx-armbian|https://github.com/ophub/amlogic-s9xxx-armbian|smart-link] * 3rd party Linux distros (manjaro, dietpi, debian, … ) usually just “supports” everything For those working, half or not working images, people are still asking us on our forums for support so we didn’t actually fix much. This means it makes little sense to not provide images at all so it might be sane to come out with some automated solution that can be used - primarily by us & our community. Working POC exists on: [https://github.com/armbian/community|https://github.com/armbian/community|smart-link] Is a dedicated repository which is holding up to 3 releases of every boards that are not end of life (EOL) or supported. For EOL we don’t provide images as they don’t build or are just obsolete, while for supported we provide stable downloads from our fast download infrastructure with torrents. This repository contains Actions scripts that builds images from nightly repository on every 6 hours. Since we easily hit API rate limits, we have to repeat builds to complete one version many times until all images are successfully uploaded. For now, releases are only uploaded to GitHub, but its possible to (ready but not enabled) upload to our infrastructure. Each targets gets 2 x CLI and 2 x XFCE desktop images in latest Debian and Ubuntu flavour. If BUILD_DESKTOP=”no” is set in the board config, then desktop images are not generated. Download link: [https://github.com/armbian/community/releases/latest|https://github.com/armbian/community/releases/latest]

Last year we concluded to shrink supported board count [https://www.armbian.com/newsflash/armbian-needs-your-help/|https://www.armbian.com/newsflash/armbian-needs-your-help/|smart-link] and stop providing community supported configuration [https://docs.armbian.com/User-Guide_Board-Support-Rules/|https://docs.armbian.com/User-Guide_Board-Support-Rules/|smart-link] . Main idea of this is to make a clean line what is supported and what not. Also an attempt to lower stress from support. But. Images that are in the system and those which are not (yet) are usually produced: * by developers individually * by 3rd party projects: [https://github.com/ophub/amlogic-s9xxx-armbian|https://github.com/ophub/amlogic-s9xxx-armbian|smart-link] * 3rd party Linux distros (manjaro, dietpi, debian, … ) usually just “supports” everything For those working, half or not working images, people are still asking us on our forums for support so we didn’t actually fix much. This means it makes little sense to not provide images at all so it might be sane to come out with some automated solution that can be used - primarily by us & our community. Working POC exists on: [https://github.com/armbian/community|https://github.com/armbian/community|smart-link] Is a dedicated repository which is holding up to 3 releases of targets that are not end of life (EOL) or supported. For EOL we don’t provide images as they usually don’t build or are just obsolete, while for supported we provide stable downloads from our fast download infrastructure with torrents. This repository contains Actions scripts that builds images from ([beta.armbian.com|http://beta.armbian.com]) nightly repository on every 6 hours. Since we easily hit API rate limits, we have to (automatically) repeat builds to complete one version many times until all images are successfully uploaded. Releases are only uploaded to GitHub and IMO it should stay this way, unless this is a problem for Chinese users? - it is possible to (ready but not enabled) upload to our infrastructure or just somewhere else then GitHub. Each targets gets 2 x CLI and 2 x XFCE desktop images in latest Debian and Ubuntu flavour. If BUILD_DESKTOP=”no” is set in the board config, then desktop images are not generated. Download link: [https://github.com/armbian/community/releases/latest|https://github.com/armbian/community/releases/latest]

Igor Pecovnik

updated the DescriptionAugust 7, 2022 at 8:18 PM

Images and support we are adding but not supporting are usually produced: * by developers individually * by 3rd party projects: [https://github.com/ophub/amlogic-s9xxx-armbian|https://github.com/ophub/amlogic-s9xxx-armbian|smart-link] * 3rd party Linux distros (manjaro, dietpi, debian, … ) usually just “supports” everything, while for those half or not working images, people are still asking us on our forums for support and ignores our support policy. It makes little sense to not provide any images so it might be sane to come out with some automated solution that can be used by our community members. [https://github.com/armbian/community|https://github.com/armbian/community|smart-link] Is a dedicated repository which is holding up to 3 releases of every boards that are not end of life (EOL) or supported. For EOL we don’t provide images as they don’t build or are just obsolete, while for supported we provide stable downloads from our fast download infrastructure with torrents. This repository contains Actions scripts that builds images from nightly repository on every 6 hours. Since we easily hit API rate limits, we have to repeat builds to complete one version many times until all images are successfully uploaded. For now, releases are only uploaded to GitHub, but its possible to (ready but not enabled) upload to our infrastructure. Each targets gets 2 x CLI and 2 x XFCE desktop images in latest Debian and Ubuntu flavour. If BUILD_DESKTOP=”no” is set in the board config, then desktop images are not generated. Download link: [https://github.com/armbian/community/releases/latest|https://github.com/armbian/community/releases/latest]

Last year we concluded to shrink supported board count [https://www.armbian.com/newsflash/armbian-needs-your-help/|https://www.armbian.com/newsflash/armbian-needs-your-help/|smart-link] and stop providing community supported configuration [https://docs.armbian.com/User-Guide_Board-Support-Rules/|https://docs.armbian.com/User-Guide_Board-Support-Rules/|smart-link] . Main idea of this is to make a clean line what is supported and what not. Also an attempt to lower stress from support. But. Images that are in the system and those which are not (yet) are usually produced: * by developers individually * by 3rd party projects: [https://github.com/ophub/amlogic-s9xxx-armbian|https://github.com/ophub/amlogic-s9xxx-armbian|smart-link] * 3rd party Linux distros (manjaro, dietpi, debian, … ) usually just “supports” everything For those working, half or not working images, people are still asking us on our forums for support so we didn’t actually fix much. This means it makes little sense to not provide images at all so it might be sane to come out with some automated solution that can be used - primarily by us & our community. Working POC exists on: [https://github.com/armbian/community|https://github.com/armbian/community|smart-link] Is a dedicated repository which is holding up to 3 releases of every boards that are not end of life (EOL) or supported. For EOL we don’t provide images as they don’t build or are just obsolete, while for supported we provide stable downloads from our fast download infrastructure with torrents. This repository contains Actions scripts that builds images from nightly repository on every 6 hours. Since we easily hit API rate limits, we have to repeat builds to complete one version many times until all images are successfully uploaded. For now, releases are only uploaded to GitHub, but its possible to (ready but not enabled) upload to our infrastructure. Each targets gets 2 x CLI and 2 x XFCE desktop images in latest Debian and Ubuntu flavour. If BUILD_DESKTOP=”no” is set in the board config, then desktop images are not generated. Download link: [https://github.com/armbian/community/releases/latest|https://github.com/armbian/community/releases/latest]

Igor Pecovnik

updated the DescriptionAugust 7, 2022 at 8:11 PM

Images and support we are adding but not supporting are usually produced: * by developers individually * by 3rd party projects: [https://github.com/ophub/amlogic-s9xxx-armbian|https://github.com/ophub/amlogic-s9xxx-armbian|smart-link] * 3rd party Linux distros (manjaro, dietpi, debian, … ) usually just “supports” everything, while for those half or not working images, people are still asking us on our forums for support and ignores our support policy. It makes little sense to not provide any images so it might be sane to come out with some automated solution that can be used by our community members. [https://github.com/armbian/community|https://github.com/armbian/community|smart-link] Is a dedicated repository which is holding up to 3 releases of every boards that are not end of life (EOL) or supported. For EOL we don’t provide images as they don’t build or are just obsolete, while for supported we provide stable downloads from our fast download infrastructure with torrents. This repository contains Actions scripts that builds images from nightly repository on every 6 hours. Since we easily hit API rate limits, we have to repeat builds to complete one version many times until all images are successfully uploaded. For now, releases are only uploaded to GitHub, but its possible to (ready but not enabled) upload to our infrastructure. Each targets gets 2 x CLI and 2 x XFCE desktop images in latest Debian and Ubuntu flavour. If BUILD_DESKTOP=”no” is set in the board config, then desktop images are not generated. Download link: [https://github.com/armbian/community/releases/latest|https://github.com/armbian/community/releases/latest]

Igor Pecovnik

updated the DescriptionAugust 7, 2022 at 8:11 PM

Images and support we are adding but not supporting are usually produced: * by developers individually * by 3rd party projects: [https://github.com/ophub/amlogic-s9xxx-armbian|https://github.com/ophub/amlogic-s9xxx-armbian|smart-link] * 3rd party Linux distros (manjaro, dietpi, debian, … ) usually just “supports” everything, while for those half or not working images, people are still asking us on our forums for support and ignores our support policy. It makes little sense to not provide any images so it might be sane to come out with some automated solution that can be used by our community members. [https://github.com/armbian/community|https://github.com/armbian/community|smart-link] Is a dedicated repository which is holding up to 3 releases of every boards that are not end of life (EOL) or supported. For EOL we don’t provide images as they don’t build or are just obsolete, while for supported we provide stable downloads from our fast download infrastructure with torrents. This repository contains Actions scripts that builds images from nightly repository on every 6 hours. Since we easily hit API rate limits, we have to repeat builds to complete one version many times until all images are successfully uploaded. For now, releases are only uploaded to GitHub, but its possible to (ready but not enabled) upload to our infrastructure. Each targets gets 2 x CLI and 2 x XFCE desktop images in latest Debian and Ubuntu flavour. If BUILD_DESKTOP=”no” is set in the board config, then desktop images are not generated.

Images and support we are adding but not supporting are usually produced: * by developers individually * by 3rd party projects: [https://github.com/ophub/amlogic-s9xxx-armbian|https://github.com/ophub/amlogic-s9xxx-armbian|smart-link] * 3rd party Linux distros (manjaro, dietpi, debian, … ) usually just “supports” everything, while for those half or not working images, people are still asking us on our forums for support and ignores our support policy. It makes little sense to not provide any images so it might be sane to come out with some automated solution that can be used by our community members. [https://github.com/armbian/community|https://github.com/armbian/community|smart-link] Is a dedicated repository which is holding up to 3 releases of every boards that are not end of life (EOL) or supported. For EOL we don’t provide images as they don’t build or are just obsolete, while for supported we provide stable downloads from our fast download infrastructure with torrents. This repository contains Actions scripts that builds images from nightly repository on every 6 hours. Since we easily hit API rate limits, we have to repeat builds to complete one version many times until all images are successfully uploaded. For now, releases are only uploaded to GitHub, but its possible to (ready but not enabled) upload to our infrastructure. Each targets gets 2 x CLI and 2 x XFCE desktop images in latest Debian and Ubuntu flavour. If BUILD_DESKTOP=”no” is set in the board config, then desktop images are not generated. Download link: [https://github.com/armbian/community/releases/latest|https://github.com/armbian/community/releases/latest]

Igor Pecovnik

updated the DescriptionAugust 7, 2022 at 8:10 PM

Images and support we are adding but not supporting are usually produced: * by developers individually * by 3rd party projects: [https://github.com/ophub/amlogic-s9xxx-armbian|https://github.com/ophub/amlogic-s9xxx-armbian|smart-link] * 3rd party Linux distros (manjaro, dietpi, debian, … ) usually just “supports” everything, while for those half or not working images, people are still asking us on our forums for support and ignores our support policy. It makes little sense to not provide any images so it might be sane to come out with some automated solution that can be used by our community members. [https://github.com/armbian/community|https://github.com/armbian/community|smart-link] Is a dedicated repository which is holding up to 3 releases of every boards that are not end of life (EOL) or supported. For EOL we don’t provide images as they don’t build or are just obsolete, while for supported we provide stable downloads from our fast download infrastructure with torrents. This repository contains Actions scripts that builds images from nightly repository on every 6 hours. Since we easily hit API rate limits, we have to repeat builds to complete one version many times until all images are successfully uploaded. For now, releases are only uploaded to GitHub, but its possible to (ready but not enabled) upload to our infrastructure. Each board gets 2 x CLI and 2 x XFCE desktop images in latest Debian and Ubuntu flavour.

Images and support we are adding but not supporting are usually produced: * by developers individually * by 3rd party projects: [https://github.com/ophub/amlogic-s9xxx-armbian|https://github.com/ophub/amlogic-s9xxx-armbian|smart-link] * 3rd party Linux distros (manjaro, dietpi, debian, … ) usually just “supports” everything, while for those half or not working images, people are still asking us on our forums for support and ignores our support policy. It makes little sense to not provide any images so it might be sane to come out with some automated solution that can be used by our community members. [https://github.com/armbian/community|https://github.com/armbian/community|smart-link] Is a dedicated repository which is holding up to 3 releases of every boards that are not end of life (EOL) or supported. For EOL we don’t provide images as they don’t build or are just obsolete, while for supported we provide stable downloads from our fast download infrastructure with torrents. This repository contains Actions scripts that builds images from nightly repository on every 6 hours. Since we easily hit API rate limits, we have to repeat builds to complete one version many times until all images are successfully uploaded. For now, releases are only uploaded to GitHub, but its possible to (ready but not enabled) upload to our infrastructure. Each targets gets 2 x CLI and 2 x XFCE desktop images in latest Debian and Ubuntu flavour. If BUILD_DESKTOP=”no” is set in the board config, then desktop images are not generated.

Igor Pecovnik

updated the DescriptionAugust 7, 2022 at 8:09 PM

Images and support we are adding but not supporting are usually produced: * by developers individually * by 3rd party projects: [https://github.com/ophub/amlogic-s9xxx-armbian|https://github.com/ophub/amlogic-s9xxx-armbian|smart-link] * 3rd party Linux distros (manjaro, dietpi, debian, … ) usually just “supports” everything, while for those half or not working images, people are still asking us on our forums for support and ignores our support policy. It makes little sense to not provide any images so it might be sane to come out with some automated solution that can be used by our community members. [https://github.com/armbian/community|https://github.com/armbian/community|smart-link] Is a dedicated repository which is holding up to 3 releases of every boards that are not end of life (EOL) or supported. For EOL we don’t provide images as they don’t build or are just obsolete, while for supported we provide stable downloads from our fast download infrastructure with torrents. This repository contains Actions scripts that builds images from nightly repository on every 6 hours. Since we easily hit API rate limits, we have to repeat builds to complete one version many times until all images are successfully uploaded. For now, releases are only uploaded to GitHub, but its possible to (ready but not enabled) upload to our infrastructure.

Images and support we are adding but not supporting are usually produced: * by developers individually * by 3rd party projects: [https://github.com/ophub/amlogic-s9xxx-armbian|https://github.com/ophub/amlogic-s9xxx-armbian|smart-link] * 3rd party Linux distros (manjaro, dietpi, debian, … ) usually just “supports” everything, while for those half or not working images, people are still asking us on our forums for support and ignores our support policy. It makes little sense to not provide any images so it might be sane to come out with some automated solution that can be used by our community members. [https://github.com/armbian/community|https://github.com/armbian/community|smart-link] Is a dedicated repository which is holding up to 3 releases of every boards that are not end of life (EOL) or supported. For EOL we don’t provide images as they don’t build or are just obsolete, while for supported we provide stable downloads from our fast download infrastructure with torrents. This repository contains Actions scripts that builds images from nightly repository on every 6 hours. Since we easily hit API rate limits, we have to repeat builds to complete one version many times until all images are successfully uploaded. For now, releases are only uploaded to GitHub, but its possible to (ready but not enabled) upload to our infrastructure. Each board gets 2 x CLI and 2 x XFCE desktop images in latest Debian and Ubuntu flavour.

Igor Pecovnik

changed the StatusAugust 7, 2022 at 8:08 PM

To Do

In Progress

Igor Pecovnik

created the IssueAugust 7, 2022 at 8:08 PM

Armbian

Armbian community automated build

Description

Checklist

Activity

Details

Assignee

Fix versions

Reporter

Story Points

Components

Priority