Concourse Feedback
Your feedback drives the Concourse roadmap! Review and vote for existing ideas or submit new ideas.
For immediate technical support, please follow this guidance to open a Service Now ticket.
Your feedback drives the Concourse roadmap! Review and vote for existing ideas or submit new ideas.
For immediate technical support, please follow this guidance to open a Service Now ticket.
Help users instantly recognize which Jira attachments (in the attachments section of Jira) are already synced to SaveIt, reducing version confusion and duplicate edits.
Right now, Jira attachments are static, giving no visual cue about whether they are synced to SaveIt. Users mistakenly treat local attachments as up-to-date and download or edit old versions, re-upload (when a version is already sent to SaveIt and is the source of the truth for that document), creating misalignment, frustration, wasted time, and duplicate efforts.
This feature improves document governance and cross-team collaboration, reducing rework caused by outdated attachments. It supports better user trust in our system and encourages correct usage of SaveIt for source-of-truth storage—key for scaling enterprise document handling and compliance.
Introduce visual indicators (e.g., icons or tags) within the Jira attachment section to show whether a file has been synced to SaveIt.
Scope includes:
Sync status icon next to each attachment
Hover tooltip explaining what the status means
Sync logic that aligns with the Forge panel display
Contextual education nudges for unsynced files
Universal display of sync status across all user roles
Effort includes FE/UX icon work, syncing logic from SaveIt’s backend, hover state handling, and shared indicator framework across roles.
Element |
Status |
|---|---|
Scope and business context clearly defined |
✅ |
Business rules and requirements captured |
✅ |
Client-specific and global criteria addressed |
✅ |
Feature rollout approach documented |
✅ (Gradual rollout, starting with synced users) |
Engineering leadership review complete |
✅ (Ready for refinement) |
T-shirt sizing completed |
✅ (M) |
Error handling expectations defined |
✅ (No icon if sync fails; fallback hover message prompts user to retry) |
Dependencies/relationships documented |
✅ (Relies on SaveIt Forge sync logic and attachment panel integration) |
Test strategy confirmed |
✅ (FE: icon visibility, hover accuracy; BE: sync status fidelity) |
Non-happy path scenarios captured |
✅ (Failed sync, duplicate uploads, unsynced attachments) |
Ready for pods to refine at story level |
✅ |
Personas:
Project Managers reviewing work items
Editors uploading attachments
Clients accessing shared files in Jira
Approximate Reach:
Applies to all Jira users interacting with SaveIt-integrated attachments
Estimated reach: 80%+ of active SaveIt-linked Jira projects
A project manager sees three attachments on a Jira ticket. Two show the SaveIt icon; one doesn’t. They skip downloading the outdated file and instead click through to the synced SaveIt version for collaborative editing.
You are now able to see exactly which Jira attachments have been synced to SaveIt—no more guessing or downloading outdated files. Clear visual icons show you when a file is up-to-date and ready to collaborate on in SaveIt. Say goodbye to version confusion and hello to confident teamwork!
| Workspace Territory | United States |
