Comments
-
Understand. I see in the video this is JMWE. Indeed in the video they show the following… I don’t have hands-on familiarity with JMWE and if/how it is auto-updating the field but will assume that it does based on the video.
-
Understand. Definitely reach out to support if this reoccurs. Question - what are you doing with the previous complete issues that land back in the backlog? If you carry them over to the next sprint can I assume they simply show in the right most column from the start of the sprint?
-
Hi @Dimman , what do you mean by auto update without reloading the page? To be clear if you are displaying an issue and the update a field that is used to trigger an automation rule, in order to see the updated field you will need to reload the page to observe the field updated by the rule. This isn’t an automation issue…
-
That looks to be Story Points
-
In JSM you do not want to move the issue to another project as it will break the connection with the customer. Rather, what you should do is use create linked issue feature which will create an issue in the other project and link the two together. You can then, if desired, use automation to keep the two in sync.
-
Hi @Craig Eves , welcome to the Community. I’m not sure what this drop down is specifically. It could have been a custom field or maybe related to Insight integration? Here is some documentation on the later - what-is-insight-in-jira-service-management-cloud
-
I did not think that was possible but maybe it depends on the actual app. I know that many apps allow you to associate the app’s capabilities at the project level. Which app are we talking about here and have you checked the docs for that app?
-
@Dai G , Atlassian is rolling out the integration of Proforma which will take a bit of time to get all cloud instances up to date. This is why the documentation provides the disclaimer at the top. With Cloud there is no ‘versioning’. The idea is that your instance is continually updated. If you have Premium you have some…
-
Ah yes! I forgot about that as I rarely use it and have not attempted for Priority. When I have a few minutes I’ll give that a try. It is odd that it was working and then stopped. I assume that what is happening is that the priority is set to the system default? Do you know if by chance the workflow has changed recently?
-
Ok and then you submit the request but it doesn’t show in the view app requests?
-
Hi @Romina Di Girolamo , I am guessing that there is an Automation rule in place for setting the priority based upon the Request type. Can you check the Automation section under project settings? Assuming this is the case please check the logs for recent failures to assess what may be going wrong.
-
And here is the Cloud version of the request- JRACLOUD-2734 . I don’t suspect that this will get implemented TBH. What I have done on some projects is to use a “latest status” custom text field and ask the team to keep it updated. I then can display this field on my filtered list on dashboards.
-
Hi @U Sravani , to be clear if you go to More in the top menu an then Apps > find new apps and then search for Zephyr Scale then Try it free then it is not installed? What do you see when you click Try it free?
-
Hi @Raghu_Moger , we’re you able to enable the account here? What do you see if you click on the ellipses?
-
Ok in that image you are showing 46 incomplete. If you are saying that these 46 issue were indeed in the right most column of your sprint when completing the sprint the something is certainly wrong and you should contact Atlassian Support directly. I am still quite curious as to he differences between the issues seen as…
-
Hi @Sjoerd van Hoof , to be clear this doesn’t present “tasks” under “stories” which was the primary inquiry of this post.
-
So when you close the sprint do you get a notification that issues are incomplete and will be moved to backlog or next sprint?
-
@cdelhom , you may wish to refer to https://www.atlassian.com/legal/sla . If you feel an SLA was missed you can request reimbursement I think.
-
Run a JQL to find all issues with the label and delete all occurrences of the label. Be sure to clear your browser cache afterwards.
-
Not to my knowledge. Since the line is deleted the comment is as well. Unfortunate. 😞
-
Hi @cdelhom , if you have submitted a ticket you should get a response soon. You might try to escalate the ticket as well.
-
@Meytal BM , can you reengage here?
-
@J B , this is a rather old post. I as wondering if this is still occurring and if not did you discover the cause?
-
No. Automation falls under Project Admin and above. It cannot be separated out.
-
You won’t find that in Free version.
-
Hmmm, this is quite odd based on what you have shown and said here. Just to confirm, you are saying that you completed the sprint and issues in the right most column ended up going back into your backlog or future spread correct? Something is missing or being overlooked here.
-
What fields do you want/need?
-
What do you mean “adding multiple attachment to widget? Can you provide more details and maybe screenshots?
-
If this is a JSM project then @Fabian Lim answer is he way to go. If this is a JSW project then the only OOTB solution would be to use a scheduled Automation rule that would run maybe every 5-10min.
-
But that only applies to JSM. This issue was posted under Jira.