Does Jira provide a view or report that show Issue history changes for multiple issues?
Example.
orginal storypoint estimate vs. current storypoint estimate
orginal fix version vs. current fix version
etc...
Community moderators have prevented the ability to post new answers.
Rather predictably, I think this is a great idea. You could do a "storypoint delta" custom field which is the difference between original and current values, or show the original version of any field.
Probably be better if JQL was more flexible about the columns it could show, and you could do derived or calculated columns...
> Maybe for performance reasons it might be better to look out for a calculated custom field implementation some day
I'm not convinced that it would be any faster... under the covers the scripted field is a calculated custom field. There is a one-time hit for script compilation, but that only happens once per script per jira restart.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We use a custom scripted field to calculate the buffered effort between a high and low estimation range. While I think there is a performance hit that comes with the addition of every custom field, we haven't seen anything spectacularly damaging to performance with the add-in of this scripted field.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The thing about conditions is that they are evaluated 3 times whenever you view an issue. Why 3 and not 1 is a bug in jira imho. So if you have an expensive condition then that's going to hurt, although I think it would be more or less the same if you wrote the condition as a java plugin. I say more or less because there is an overhead in calling groovy classes from java and vice versa, but it's so small compared to the impact of jdbc or Lucene as to be diminishing to zero.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As I know JIRA doesn't support history printing or export. Good news is that there is a free add-on supports history printing of issues. Check it out the plug-in features.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I don't think it does so out of the box. To access the default reports, you can go to Projects (tab)> Reports (right side top of app). There are a number of plug-ins, though, that might support your needs. Search here https://plugins.atlassian.com on "reports".
A manual work-around to get the info that you need is to take a baseline export on the first day of your iteration/ version, and compare exports as you progress.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The SQL for JIRA plugin supports it out-of-the-box
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is there any way to get all the initials values of all fields of issue when issues was created. We have history tab, but that does'nt give us the original values.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If the value has not changed in the history, then the current value is the original value. You can also take the current set of values and revert all the changes in the history tab to get the original values
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Community moderators have prevented the ability to post new answers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.