Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-33256

Restrict Post Functions to Sensible Timings

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Do
    • None
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      JIRA currently allows you to have post functions in illogical orders that will get people into trouble.

      For example, you could update a field in a post function, but have it happen after the history is written and indexing done. This means that the issue will not be searchable using that data in that field, and the edit of the field will never actually show up in the issue history tab. If a plugin (such as GreenHopper) is trying to use this data for calculations it will be invalid - as the field will be in a state that the history does not show how it got there.

            Unassigned Unassigned
            clepetit ChrisA
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: