Details
-
Type:
New Feature
-
Status: To-Do (View Workflow)
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Story Points:1
-
Epic Link:
Description
Situation: When I uploaded bam files and their indexes to CyVerse/BioViz Connect and then made the bam files public, the index should have also become public automatically. See linked issue below. This does not appear to have happened.
Task: Investigate if bam index files are automatically being made public when their respective bam file is made public. If the indexes are not becoming public, then change this ticket to a "Fix" issue and address the issue.
Implement a change where bam index files become public when a user makes the respective bam file public in the Manage Link right panel.
Attachments
Issue Links
- blocks
-
IGBF-1654 Make index files public automatically
-
- Closed
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Epic Link | IGBF-2376 [ 18533 ] |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Summary | Investigate index files not becoming public automatically | Implement index files made public with respective bam file |
| Description |
Situation: When I uploaded bam files and their indexes to CyVerse/BioViz Connect and then made the bam files public, the index should have also become public automatically (see Task: Investigate if bam index files are automatically being made public when their respective bam file is made public. If the indexes are not becoming public, then change this ticket to a "Fix" issue and address the issue. |
Situation: When I uploaded bam files and their indexes to CyVerse/BioViz Connect and then made the bam files public, the index should have also become public automatically (see Task: -Investigate if bam index files are automatically being made public when their respective bam file is made public. If the indexes are not becoming public, then change this ticket to a "Fix" issue and address the issue.- |
| Description |
Situation: When I uploaded bam files and their indexes to CyVerse/BioViz Connect and then made the bam files public, the index should have also become public automatically (see Task: -Investigate if bam index files are automatically being made public when their respective bam file is made public. If the indexes are not becoming public, then change this ticket to a "Fix" issue and address the issue.- |
Situation: When I uploaded bam files and their indexes to CyVerse/BioViz Connect and then made the bam files public, the index should have also become public automatically (see Task: -Investigate if bam index files are automatically being made public when their respective bam file is made public. If the indexes are not becoming public, then change this ticket to a "Fix" issue and address the issue.- Implement a change where bam index files become public when a user makes the respective bam file public in the Manage Link right panel. |
| Issue Type | Bug [ 1 ] | New Feature [ 2 ] |
| Sprint | Fall 3 2022 Sep 26 [ 155 ] |
| Description |
Situation: When I uploaded bam files and their indexes to CyVerse/BioViz Connect and then made the bam files public, the index should have also become public automatically (see Task: -Investigate if bam index files are automatically being made public when their respective bam file is made public. If the indexes are not becoming public, then change this ticket to a "Fix" issue and address the issue.- Implement a change where bam index files become public when a user makes the respective bam file public in the Manage Link right panel. |
Situation: When I uploaded bam files and their indexes to CyVerse/BioViz Connect and then made the bam files public, the index should have also become public automatically. See linked issue below. (see ). This does not appear to have happened.
Task: Investigate if bam index files are automatically being made public when their respective bam file is made public. If the indexes are not becoming public, then change this ticket to a "Fix" issue and address the issue.- Implement a change where bam index files become public when a user makes the respective bam file public in the Manage Link right panel. |
| Description |
Situation: When I uploaded bam files and their indexes to CyVerse/BioViz Connect and then made the bam files public, the index should have also become public automatically. See linked issue below. (see ). This does not appear to have happened.
Task: Investigate if bam index files are automatically being made public when their respective bam file is made public. If the indexes are not becoming public, then change this ticket to a "Fix" issue and address the issue.- Implement a change where bam index files become public when a user makes the respective bam file public in the Manage Link right panel. |
Situation: When I uploaded bam files and their indexes to CyVerse/BioViz Connect and then made the bam files public, the index should have also become public automatically. See linked issue below. This does not appear to have happened.
Task: Investigate if bam index files are automatically being made public when their respective bam file is made public. If the indexes are not becoming public, then change this ticket to a "Fix" issue and address the issue. Implement a change where bam index files become public when a user makes the respective bam file public in the Manage Link right panel. |
| Status | In Progress [ 3 ] | To-Do [ 10305 ] |
The
IGBF-1654ticket was part of the original build of BioViz Connect prior to moving to Django. The functionality of 1654 was not copied over to the current version of BioViz Connect, and the code would need to be re-implemented in its entirety, so this is not a bug but would instead be a new feature.I have made this ticket an implement ticket and have moved it to the backlog as it is a good idea to eventually implement.