Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-2398

expose full history details through the history api

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Major
    • jBPM 4.5
    • None
    • Runtime Engine
    • None

    Description

      expose the history that is in the database through the api

      Attachments

        Issue Links

          blocks

          Feature Request - Feature requests from customers and/or users JBPM-2873 Support LIKE operator in Query interfaces

          • Optional - The request should be considered desirable but is not an immediate necessity.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. JBPM-2417 allow for programmatic way to specify authentication through service api

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open
          incorporates

          Feature Request - Feature requests from customers and/or users JBPM-2896 Add the name of the task to HistoryTask

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Feature Request - Feature requests from customers and/or users JBPM-2914 query task comment by process instance id

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved
          is related to

          Task - Represents a small unit of work that is not end-user facing. JBPM-2568 review history based on user feedback

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open
          relates to

          Feature Request - Feature requests from customers and/or users JBPM-2442 Review task history details and add new information where needed

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved

          Feature Request - Feature requests from customers and/or users JBPM-2914 query task comment by process instance id

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved

          Activity

            People

              swiderski.maciej Maciej Swiderski (Inactive)
              tom.baeyens Tom Baeyens (Inactive)
              Votes:
              10 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: