Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-1654

As DEV, I can define a follow up date for tasks

    • Icon: Feature Request Feature Request
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 7.1.0, 7.1.0-alpha2
    • None
    • engine
    • None

      AT:

      • follow up date for tasks is available for all APIs
      • Docs are updated
      • History is updated
      • Upgrade Scripts are updated

      Motivation:

      Typically for Tasks there are two dates which almost task management tools know, I added a screenshot of Outlook to show them there (in German):

      • Beginnt am (starts at)
      • Fällig am (due at)

      With dueDate and followUpDate we are perfectly capable of handling this in the Task Management - even in situations where we do not hace processes (like in case management for example). This is why I like this feature so much.

        This is the controller panel for Smart Panels app

            [CAM-1654] As DEV, I can define a follow up date for tasks

            I start working on a Pull request for this.

            Bernd Ruecker added a comment - I start working on a Pull request for this.

            Bernd Ruecker added a comment - - edited

            Changed database, added two columns

            ACT_RU_TASK: FOLLOW_UP_DATE_ timestamp
            ACT_HI_TASKINST: FOLLOW_UP_DATE_ timestamp

            Bernd Ruecker added a comment - - edited Changed database, added two columns ACT_RU_TASK : FOLLOW_UP_DATE_ timestamp ACT_HI_TASKINST : FOLLOW_UP_DATE_ timestamp

            Bernd Ruecker added a comment - - edited

            I send a pull request in a minute containint:

            • TaskEntity
            • HistoricTaskInstanceEntity
            • both Queries (including sorting)
            • database create and update scripts (7.0 -> 7.1)

            I actually could not test all update scripts / databases, but had a really close eye on it so Jenkins should be happy with it.

            For REST docs I will commit the docs after the pull request is accepted - as I do not have a fork of the docs ready. Hopefully OK? Or do you want me to do a pull request there as well?

            For the docs the problem is that we lack any concept "Task" in the docs at the moment - so there is no hook to add it. So either we move that to an own issue (which I would vote for) - or I write a Task concept part for the docs.

            Bernd Ruecker added a comment - - edited I send a pull request in a minute containint: TaskEntity HistoricTaskInstanceEntity both Queries (including sorting) database create and update scripts (7.0 -> 7.1) I actually could not test all update scripts / databases, but had a really close eye on it so Jenkins should be happy with it. For REST docs I will commit the docs after the pull request is accepted - as I do not have a fork of the docs ready. Hopefully OK? Or do you want me to do a pull request there as well? For the docs the problem is that we lack any concept "Task" in the docs at the moment - so there is no hook to add it. So either we move that to an own issue (which I would vote for) - or I write a Task concept part for the docs.

            Bernd Ruecker added a comment - - edited

            Here is the Pull Request for the feature: https://github.com/camunda/camunda-bpm-platform/pull/57

            REST docs will be added as soon it is accepted.

            Bernd Ruecker added a comment - - edited Here is the Pull Request for the feature: https://github.com/camunda/camunda-bpm-platform/pull/57 REST docs will be added as soon it is accepted.

            Bernd Ruecker added a comment - Pull request for REST docs: https://github.com/camunda/docs.camunda.org/pull/20

            What I did not add was the Property on the Modeler Panel. Actually it would be pretty hard for me to create a pull request for this - but maybe a good exercise Let me know if you would like to have it as well.

            Bernd Ruecker added a comment - What I did not add was the Property on the Modeler Panel. Actually it would be pretty hard for me to create a pull request for this - but maybe a good exercise Let me know if you would like to have it as well.

            no nee to change the modeler, we can provide that with the next modeler release

            Robert Gimbel added a comment - no nee to change the modeler, we can provide that with the next modeler release

              sebastian.menski Sebastian Menski
              gimbel Robert Gimbel
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: