Skip to content

Descriptive Fields #334

Description

@marlinhares

Description

Following Screens:

  • add new Client
  • add new repo
  • add new plugins entrances (each added: database, s3, scripts, etc)

All of then should have a descriptive field to elucidate their objectives.

This will help a lot when multiple people work on the same team managing the backups tasks.

Use Case

Multiple guys on the same team.
When we have multiple repositories, multiple plans, many scripts and different databases.
It is easy to forget what is the true intent of a script, repo, database, etc. So with a descriptive field there, the creator can dissert the original obective of that entity. It will help managing the tasks

Alternatives Considered

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions