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

review history based on user feedback

    XMLWordPrintable

Details

    • Task
    • Resolution: Unresolved
    • Major
    • jBPM 4.x
    • None
    • None

    Description

      Ronald mentioned a lot of questions and activity around history. This issue is a reminder that we have to look into this topic in the 4.3 jira period (1st half of november)

      https://jira.jboss.org/jira/sr/jira.issueviews:searchrequest-printable/temp/SearchRequest.html?query=history&summary=true&description=true&body=true&pid=10052&status=1&tempMax=25

      We should try to get an overview of what exactly the history related questions/issues are and find out how we can address them. Then translate that into concrete jira issues that can be prioritized.

      Attachments

        Issue Links

          is blocked by

          Feature Request - Feature requests from customers and/or users JBPM-2576 Extending HistorySession - add public getters in HistoryEvents

          • 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
          relates to

          Feature Request - Feature requests from customers and/or users JBPM-2499 View ended ProcessInstance missing

          • 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-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-2515 End activityname not accessible through History API

          • 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-2506 add variable declarations

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

          Bug - A problem that impairs or prevents the functions of the product. JBPM-2495 No history recorded for custom activities

          • 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

          Bug - A problem that impairs or prevents the functions of the product. JBPM-2577 QuerySyntaxException in HistoryService

          • 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

          Task - Represents a small unit of work that is not end-user facing. JBPM-2398 expose full history details through the history 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.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. JBPM-2415 add declaration of process variables

          • 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

          Task - Represents a small unit of work that is not end-user facing. JBPM-2416 introduce task audit capabilities

          • 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

          Activity

            People

              Unassigned Unassigned
              tom.baeyens Tom Baeyens (Inactive)
              Votes:
              5 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: