Skip to content

fix: fixed first time startup issue #99

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
+5 −3
Open

fix: fixed first time startup issue #99

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions .gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,9 @@ bin/fern-platform
# Temporary Dockerfile created by Makefile
Dockerfile.fern-platform

# ide
*.idea

# Git files
.git-authors

Expand Down
5 changes: 2 additions & 3 deletions migrations/000015_create_jira_connections_table.up.sql
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,6 +45,5 @@ COMMENT ON COLUMN jira_connections.is_active IS 'Whether the connection is activ
COMMENT ON COLUMN jira_connections.last_tested_at IS 'Timestamp of last connection test';
COMMENT ON COLUMN jira_connections.deleted_at IS 'Soft delete timestamp';

-- Grant permissions to app user
ALTER TABLE jira_connections OWNER TO app;
GRANT ALL PRIVILEGES ON TABLE jira_connections TO app;
-- Note: Table ownership and privileges are handled by the database connection user
-- The table will be owned by the user running the migration (configured in config.yaml)
Copy link
Collaborator

@anoop2811 anoop2811 Nov 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add this change as a new sql instead of changing existing one so as not to cause any migration issues

Loading