Bill Sheboy Expert

Hi @Georg Gruber -- Welcome to the Atlassian Community! First thing: I am a Jira user, not a vendor of add-ons. Next, I haven't done a sync between Jira cloud instances before. With those disclaimers out of the way... There appear to be a few products in the marketplace to sync between instances, which you may review here:…

Hi @David S_ Rogers -- Welcome to the Atlassian Community! For an issue like this, it can help to include some screen images so the community can see what you are describing. To help further, would you please answer: * What version of Jira are you using? * What dashboard gadget are you using which is showing the incorrect…

HI @Stepan Karpinskiy -- Welcome to the Atlassian Community! I wonder if what you are seeing may be related to this open defect: https://jira.atlassian.com/browse/I18N-2724 Best regards, Bill

Hi @Patrick Roberts -- Welcome to the Atlassian Community! There were a few older and newer reports on this... Some things to check... * Is only one person having this symptom, or are there others? Is that user using the new or the old issue view? If new, ask them to try to switch to the old view. (There was recently a fix…

Hi @Sai Gangadhar It is unclear to me what problem you are trying to solve. Would you please explain further? Subtasks are normally detailed implementation parts of a larger work item, and not releasable to production on their own. And so, they wouldn't have story point sizing; their parent item (the story) would have the…

Hi @Brian Kelly Jira is a tool to help teams collaborate to manage their work. You seem to be asking a larger question about how your team should work. You could probably start with how do you teams work today to transition completed work to production: * Do you have separate delivery, operations, and support teams? * If…

Hi @Michelle Mundy I did not see any open defects for this symptom in the public backlog, so I suggest that you submit a support ticket for it. You should be able to do that as the site admin. https://support.atlassian.com/contact/#/ Once you hear back from support, please post back here what you learn. Thanks! Best…

Hi @Ameeq Asrar -- Welcome to the Atlassian Community! What problem are you trying to solve? I am assuming for the moment you are using Scrum, not Kanban... If so, to me the scrum reporting you describe seems accurate, and this information may help your team to decide how to improve your processes. And tell you how long…

Hi @Daniel Sanchez -- Welcome to the Atlassian Community! There appear to be marketplace add-ons to help with this, but there is also documentation from Atlassian. Have you looked over this page yet: https://confluence.atlassian.com/adminjiraserver/migrating-jira-applications-to-another-server-938846962.html Best regards,…

Thanks for that information... Timing problems can occur in single rules also, such as the create issue trigger, where all of the issue data may not be available when the event is caught. The work-around for that is to immediately re-fetch. This seems different... You have two rules, attempting to trigger in close timing…

Hi @Daniel Loewenstein I have definitely encountered race conditions in rules, due to the asynchronous processing. The rule structure can impact what matters and when, especially with branches and conditions. Would you please provide an image of your complete rule? That may provide some context for ideas. Regarding the…

That seems correct. Here is a related suggestion for server version, which you may vote for or watch: https://jira.atlassian.com/browse/JRASERVER-68763

Just to confirm, @marco espinoza are the two different issues ("Customer repayment" and "Repayment 30 days") in one or two Jira projects? Knowing that will help guide suggestions. Thanks!

Yes, I believe that is possible. * Trigger: issue created * Condition: trigger issue's component does not contain "Rollout" already * Branch: on the parent epic* Condition: epic's component contains "Rollout" * Actions... use the techniques we already noted to add "Rollout" to the trigger issue Please try it and see what…

Hi @roxana.garcia Are you using a classic or NextGen project? For a classic project, drag-and-drop works when you are ordering by Rank, using that to prioritize the work items. If your board's filter ends with ORDER BY Rank that will work as you describe. Best regards, Bill

Brandon, I believe that locked custom fields are the built-in ones which are required for Jira to work, or fields added by an add-on. They should not be altered (unlocked). Please look here for more details: https://support.atlassian.com/jira-cloud-administration/docs/what-are-locked-custom-fields/ Did you add your custom…

Hi @Brandon Kwock I believe that Flagged is the name of a built-in field (the flag icon). If you rename your field does this still happen? Best regards, Bill

Hi @Эдуард Назарук -- Welcome to the Atlassian Community! Why do 2 people need to be assigned to the task? What problem are you trying to solve? Issues in Jira can only have one assignee. When teams need to somehow track who participated on an issue, they could add a custom user field, such as Additional Assignees,…

Hi @Jordan Trinklein I have some process and Jira questions that might help the community answer your request better: * Are you using Classic or NextGen projects in Jira? * For the work which affects both teams, what does "affects" mean? That is, do they just need to see progress, or are both of the teams participating in…

Hi @Glen I have not done a VSM in Jira, although there might be a marketplace add-on for it. Although I didn't find one after a quick search. Some challenges of doing a VSM in Jira include the decision point entry, measurement information capture, and having multiple people updating the columns (to approximate steps)…

Hi @[deleted] I am not using this add-on, and I didn't see anything in community posts about answers to your question. You may want to contact the vendor's support directly for this request. Here is their information from the markeplace:…

Hi @[deleted] For something like this (and the evolving new issue view) you may want to ask the vendor's support directly. Here is their information from the marketplace: https://marketplace.atlassian.com/apps/1216451/smart-checklist-for-jira-enterprise?hosting=cloud&tab=support Looks like the same contact for the paid and…

Nope, and there are several defects/suggestions to add triggering on Epic Link changes:…

Hi, Dan. Correct; it does not appear to be possible yet. The suggestion you noted is for Jira Server, and I did not find a corresponding one for Cloud. You may add that suggestion in that same backlog by selecting Create at the top of the page. I recommend then adding a comment to link the two items (or put it in the…

Hi @harainye Please consider using Get Edit Issue Metadata to determine what can/cannot be edited (such as issueType). I do not have server version so I cannot check this one for you. https://docs.atlassian.com/software/jira/docs/api/REST/8.0.2/#api/2/issue-getEditIssueMeta Best regards, Bill

Hi @Cédric Cox If I am understanding your question, you are using created variables within the rule and the date functions are not working. Is that correct? If so, I suspect that the created variables are strings, and so you may need to convert them to a date first, such as with {{myVariable.toDate}} You may check progress…

Hi @Emiliano I recommend marking/voting that defect as "Affects my team", and perhaps add a comment as well regarding impacts to your team. You will then get updates on the defect's progress and the support team will have more information to help with triage. Thanks! __Bill

I expect that the design is "evolving" more likely than a defect. ;^) If you see a specific problem with the change please consider helping out the community by having your site admin submit a defect to support: https://support.atlassian.com/contact/#/ Thanks!

Well done diagnosing the issues! The action Log to write to the audit log can help solve such problems also. For example, write pieces of JSON or field values to the log as you work to see where there are problems. If this approach helped solved your question, please mark it as solved. That will help others in the…

Hi! It is this one: {{firstJson}} , { "name": "{{ "Rollout_Portugal" }}"} I gave as an example using a field from the issue. When you are using a hard-coded value you can remove the extra brackets. Please try this one: {{firstJson}} , { "name": "Rollout_Portugal"} My apologies that my example led you astray. __Bill