Marc -Devoteam- Community Champion

Hi @Loveleen Margareth As seen in the sprint report, you added on my request, I think that went wrong this time. The red line in the report starts at 8 points and after start the line climes to 135, so all issues have been added after sprint start. If all issues would be in the sprint from the start the line would have…

Hi @William Ramaki Can you show me a screenshot of the board that has this setting? As the issue you are subscribing is an open issue at Atlassian See: https://jira.atlassian.com/browse/JWMCLOUD-111

Hi @Vincent Yes the column order in a Sprint board is key.

Hi @Vincent So your config is wrong on your sprint board. the status Done should be in the last column. That is where for your item in a sprint is marked as complete. In you board this is the status "Note", not the status "Done".

Hi @Kevin bedeau Please look at the page that @Nic Brough -Adaptavist- added in his reply. You Confluence version is EOL on 17/08/2023. So the 14 day warning you are getting is the end of support date.

Hi @Vincent This is your workflow. On you project you have an Active Sprint board. what is the configuration of your columns there. Example:

What does the configuration of the plan say.

Hi @Nikola Chakalov Welcome to the community. To me it seems like there is an automation rule on the project that does this or a post function in the workflow is the trigger for this. If you are not a Jira admin or project admin, please let your admin look into the issue.

Hi @Vincent What column are in your sprint board and what WF status is on the last column? 

Hi @Markus W_ BENES All Smart Values for Jira Automation in Server and DC See sections * issue.comments * comment

Hi @Vincent What is the configuration of your Sprint board and in what status are your issues. Seems to me like your issues are not burned. Can you check your sprint report and burn-up or burn-down reports. Because closing a sprint and all issues are in the next mean that they were not marked as completed in the previous…

Hi @William Ramaki What type of projects are those? Work Management or other?

Hi @Marcel Kaiser I would reach out to Atlassian via support. There might be some information here. But it all runs on the AWS platform so I would also look into how Amazon has described this in their security documentation

Hi @PeterGraebner Are you able to send screenshots? What I do expect is that the create screen used on the issue type Test has a field called Feature Team. This is a field in Jira not related to Xray. If there are options in this field, please check with your Jira administrator, he will be able to values for this field.

Hi @William Ramaki I checked, but there are no options to do this. Only in the list option this is visible.

Hi @Loveleen Margareth You can't anymore. Your sprint has been finalised. The report can't be adjusted anymore If it was still an open sprint you could have stopped the sprint and deleted this sprint and create a new one and add all issues before starting the sprint.

Hi @Loveleen Margareth , I see why the initial commitment was 8, this was the only issue in the sprint on starting. All issues have been added after the sprint start. If they would have been in the sprint from the start your burn-up report would show the start to work scope at 135 not at 8. You see the red line moving to…

Hi @Kelli Archer What is the last time the program was synchronised?

Hi @Dainius K_ There is not option in AQL (Asset Query Language) to search the history of an object.

Hi @nibansal Welcome to the community. PlantUML options are not default in Confluence, but achieved with a 3rd party add-on. I would contact your administrator. As it seems that the license of the add-on expired, the error reltaes to this.

Hi @Vipul I think the JSON is wrong here: {{#=}}{{issue.worklog.timeSpent.divide(issue.fields.originalEstimate).multiply(100)}}{{/}}".toString() I think it could be: {{#=}}{{issue.worklog.timeSpent}} / {{issue.fields.originalEstimate}} * 100{{/}}".toString()

Hi @Loveleen Margareth , I see why the initial commitment was 8, this was the only issue in the sprint on starting. All issues have been added after the sprint start. If they would have been in the sprint from the start your burn-up report would show the start to work scope at 135 not at 8. You see the red line moving to…

Hi @Loveleen Margareth Has there been a change on the projects Workflow and/or Sprint Board? If there was and a previously used status was removed from the flow and the board, this can happen. Are you also able to share the sprint report?

Hi @Matharoo_ Daljeet singh Jira has no wiki pages. Pages in a project are Confluence pages. See the Confluence Cloud Rest API

Hi @Dang Thi Thuy Tien See the suggestion from @Fabio Racobaldo _Catworkx_ The DC option was on firing an SQL script on the DB. On Cloud there is no DB access.

HI @Vinícius Ferrão Is there an email address applied to the CC field, this would explain why

Hi @ghazal pansari Welcome to the community. The similar request feature is only available for Jira Cloud. Jira DC does not have this functionality (and likely will not get this).

Hi @Małgorzata Adamska-Piotrowska I don't see how, unless not using a number field as than can't contain other information than a number.

Hi @Małgorzata Adamska-Piotrowska I see in your reply to @Kseniia Trushnikova that customfield_22188 is a number field. Then prettyPrin can't work as you store the result in a number field, that can only contain a number. I think you should use a text field instead

Hi @Javier Eduardo Marín Fernández I expect that the user who needs to be the reporter set in the payload of the webhook?