Code Monkey home page Code Monkey logo

checklist's People

Contributors

kullervo16 avatar

Stargazers

 avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

checklist's Issues

Tags should not be case sensitive

We can create tags with uppercase and lowercase. Then we can create ACC, Acc and acc tags. It allows "duplicate" tags.

The application should avoid this. If a ACC tag already exists then the acc and Acc tags should not be created. The application should instead use the ACC tag.

Template versionning

It would be great to have a version number in the template. Then the application could check if the version number we provide is the same as the one in the deployed template.

It would also great that changes made on checklist could be pushed on Git repo by the app itself.

Tag cloud should only contain relevant tags

Only tags that are not common to the already selected checklist should be listed in the tag cloud. It means that if there is 3 checklists and the 3 checklists have the tag1 tag, the tag1tag will not be shown in the tag cloud.

It also allow the user to see when there is no more filter to apply aka when there is no more way to filter the remaining checklists.

support for template parameters

adding template parameters allows us to directly create the commands that can be copy pasted...

Let's say you create a command

${deployment_folder}/bin/myJob.sh --action=${my action}

then the user still needs to know where it's deployed and what action to take.. if we could specify this in when the template is instantiated, the user would see an action like

/opt/myProgram/bin/myJob.sh --action=ruleTheWorld

which can be copied and executed.

We should be able to manually close a checklist

If a problem occurs during deployment by example and the problem cannot be fixed, the only way to close the checklist is to mark each step with a problem. A close button could do it for us.

Error raised when using more than one / in the checklist id

The checklist app do not work if we set a template id with more than one /

ex : /vas/governance/development/architectureCheck

It is also impossible to delete a checklist template with a name like that..

Possible Quick fix : do not allow template name with more than one /

No tag managment screen

There no screen to manage tags. There is no way to change Acc tags to ACC tags for every checklists. We have to do it manually for now.

Be able to hide subchecklist in the template view

When creatint a new checklist, we are mainly interessed in primary checklist (sub checklist cannot be instantiated alone).

It should be more user friendly if we could (default behaviour) hide the subchecklists from the template view.

mattermost integration

It would be nice to have a mattermost integration.. The idea is that that way, your mattermost-driven team does not need to watch the checklist and you can use the search functionality provided by mattermost to retrieve the checklist in question

The system would need to support:

  • creation of mattermost channels
    • destination incoming webhook
    • checkboxes to select which messages you want
      • begining of the checklist
      • succeeded step
      • failed step
      • completion of the checklist
  • the abitility to assign one or more channels to an instantiated checklist (via dropdown selection of the configured channels)
  • message should include a link so that you can navigate directly to the checklist page form the message

Autocomplete tags

When we have to enter a tag, the application should autocomplete the user's input. Then we will have less duplicate values (MAFVO/VO, ACC/acceptance, PRD/production,...).

Exception when error text contains YAML relevant tokens

13:04:07,519 SEVERE [kullervo16.checklist.model.persist.TemplatePersister](default task-21) Error while parsing /opt/checklist/checklists/deployment/deployment/0b58f7e7-1ce2-4025-a62f-9990282928c4: com.esotericsoftware.yamlbeans.YamlException: Error parsing YAML.

support for questions

At the moment, there is only support for actions. Sometimes you just want to ask the user a question, and keep track of the answers.

The possible answers should be:

  • free format text
  • radio button (1 selection)
  • check boxes (multiple selection)

The results should remain shown when the question is answered. The various options when displaying the template

New step in standard deployment cheklists

Currently we are surprised by a chat that our deployment is done.

It would be a good thing if the first step of the checlist is: "Contact the requestor that the deployment will be started".

This way we can better prepare and follow up ...

Tags with directory and template name should be automatically created when a new checklist in instanciated

When the application instantiate a new checklist, 2 tags should be created automatically: one with the name of the directory and one with the name of the checklist.

When a sub checklist is instantiated, we should do the same. But we should exclude the 2 tags automatically created for the parent checklist from the tags inheritance.

This will fix the problem of unicity of the checklists when a sun checklist in instantiated.

Detail of problem not shown

When a problem occurs on a step, we can add a comment. Then the error counter is incremented each time a comment is added. But there is no way to see the comment, only the counter value.

Propose to go back to the parent when subtemplate is complete

Some users did not grasp the fact that they ended up in a subtemplate... so at the end, they were kind of lost because they did not know they should go back up and continue...

Add an indication that the subchecklist is complete, and invite the user to go back to the parent...

options not shown anymore

from mail of @kernixski
deployment.yml.txt

Quelques problèmes rencontrés.

Dans IE, quand je clique sur "Select" dans le menu, il y a une boucle infinie de redirections.

Dans Firefox, quand je clique sur un élément du nuage de tags, le tag n'est pas sélectionné.

Avec Chrome, quand j'instancie la checklist /deployment/deployment, il ne me pose pas la question "Is this the first deployment of the application?" Bizarre, non ?

Add AutoFresh as POST parameter

Would it be possible to add the "Autorefresh" as POST parameter. So we can use the feature of automatic scrolling to the first open step on automated systems.

thanks

Invalid model causes template list to be empty

Caused by: java.lang.ClassCastException: java.lang.String cannot be cast to java.util.Map
963 at kullervo16.checklist.model.Step.(Step.java:107)
964 at kullervo16.checklist.model.persist.TemplatePersister.handleData(TemplatePersister.java:81)
965 at kullervo16.checklist.model.persist.TemplatePersister.checkAndLoadDataFromFile(TemplatePersister.java:57)
966 at kullervo16.checklist.model.Template.checkAndLoadDataFromFile(Template.java:89)
967 at kullervo16.checklist.model.Template.getDescription(Template.java:68)
968 at kullervo16.checklist.repository.TemplateRepository.getTemplateInformation(TemplateRepository.java:95)
969 at kullervo16.checklist.rest.TemplateService.listTemplateNames(TemplateService.java:56)

save templates upon update

At this moment the update of a template directly has effect (if the template is valid). Backup the previous version so that a manual rollback can be initiated if needed

Bad resource name for checklist/get

/checklist/rest/checklist/get?id=checklist_id is not a good REST URI. Should be /checklist/rest/checklists/checklist_id

GET /checklist/rest/checklists/checklist_id should return the checklist.

Add a flag to mark a checklist template as "SubCheckList only"

Some checklist template should only be used as subchecklist.

In the template of such a subchecklist, we should give meta data to flag this checklist as subChecklistOnly

With this flag, a template should not be usable from scratch.. but only usable from another mother checklist.

In the template and checklist screen, we could also add a filter to hide (default) such *subchecklist only" templates

GET /checklist forbidden

GET /checklist should redirect the browser on an existing page (select.html or templates.html in my opinion).

New tag modal window not shown

When I create a new checklist based on /deployment/deployment and I add the existing openshift tag 2 or three times, then the modal window disapears and I am blocked (no action possible). Then only way to leave this state is to refresh the page.

As the problem does not appears when I change the tag name each time, it is a very minor bug.

keep track of who makes a change

At this moment, you cannot see who executed a step (or when). Determine the user via the hostname of the client (will work fine in most enterprise networks, other user management could be added later on)

Store the information on the following actions:

  • execute a step
  • create a checklist
  • update a template

No way to filter checklists with more than one tag

It should be great to filter checklists with more than one tag.

Neither checklist/rest/checklist/list?tag=tag1&tag=tag2 nor checklist/rest/checklist/list?tag=tag1,ag2 seems to work.

checklist/rest/checklist/list?tag=tag1&tag=tag2 should work.

Or even better: checklist/rest/checklist/list;tag=tag1,tag2 ;o)

Filtering from the checklist overview

When we click on a checklist's tag in the checklist overview, instead of opening the checklist the application could filter the checklists list. By example, clicking on the ACC tag of a checklist should add the ACC tag to the tags fragment param of the URL.

We should be able to reopen a step

The user can do mistakes. If the user select the wrong answer for a question, there is no way to change it. A closed step should be reopenable if the following step is not closed.

Show checklist when the checklist overview contains only one checklist

Then when we make a search though the URL (with the iDeploy ticket number by example), the browser will be redirected to the checklist.html page when the list contains only one item. Will be useful for a tool like iDeploy to generate the reference to the checklist, and handy for the user because he does not have to click on the checklist item.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.