Ste Wright Community Champion

Comments

  • Hi @Yatish Madhav I would contact https://support.atlassian.com/ in this instance! It's a more specific issue and they'll be best placed to advise. Ste
  • Hi @Synergy Administrator I'm afraid for these the native Dashboards won't allow for this - for the reasons mentioned above in regards to permissions and issue visibility. You would need to look into utilising a report tool which can visualise this data externally - like EazyBI :) Ste
  • Awesome! The Status Page has also now been updated if you run into any further issues :) Ste
  • No worries :) The incident has now been posted on the Status Page; you can keep track of its progress from there! Ste
  • Hi @Synergy Administrator Can I confirm you want to: * Expose a Jira Dashboard to an external user but... * Not allow them to see the issues within the project ^ If this is the case, I don't believe this is possible. A dashboard is a visual representation of an issue filter. To see these results, a user needs to have at…
  • Hi @Yatish Madhav Just to add - the Status Page has now been updated with recorded incidents. This should help with sending a notification to your users :) Ste
  • Awesome! The Status Page has also been updated; you can now view the details of the incident if required :) Ste
  • Hi @Yatish Madhav This isn't the same issue, given the question was from April :) I've left a comment on your newer question. Ste
  • Hi @Seema K Atlassian is aware - I've been told an internal incident report has been raised. Our instance also went down but it seems like its back now - so keep trying! Whilst it has not yet been updated, you can also check for issues via: https://status.atlassian.com/ Ste
  • Hi All, Atlassian is aware - I've been told an internal incident report has been raised. Our instance also went down but it seems like its back now - so keep trying! Whilst it has not yet been updated, you can also check for issues via: https://status.atlassian.com/ Ste
  • Hi @Will McFarlane , @Lars Schwede , @Xyz , Atlassian is aware - I've been told an internal incident report has been raised. Our instance also went down but it seems like its back now - so keep trying! Whilst it has not yet been updated, you can also check for issues via: https://status.atlassian.com/ Ste
  • Hi All, Atlassian is aware - I've been told an internal incident report has been raised. Our instance also went down but it seems like its back now - so keep trying! Whilst it has not yet been updated, you can also check for issues via: https://status.atlassian.com/ Ste
  • No worries :) Ste
  • Hi @Yatish Madhav Atlassian is aware - I've been told an internal incident report has been raised. Our instance also went down but it seems like its back now - so keep trying! Whilst it has not yet been updated, you can also check for issues via: https://status.atlassian.com/ Ste
  • Hi @SEO_AddA Atlassian is aware - I've been told an internal incident report has been raised. Our instance also went down but it seems like its back now - so keep trying! Whilst it has not yet been updated, you can also check for issues via: https://status.atlassian.com/ Ste
  • Hi @Rıfat Barış KUŞCU Atlassian is aware - I've been told an internal incident report has been raised. Our instance also went down but it seems like its back now - so keep trying! Whilst it has not yet been updated, you can also check for issues via: https://status.atlassian.com/ Ste
  • Hi @Adrian Blaga Atlassian is aware - I've been told an internal incident report has been raised. Our instance also went down but it seems like its back now - so keep trying! Whilst it has not yet been updated, you can also check for issues via: https://status.atlassian.com/ Ste
  • Hi @gedeon.medina Atlassian is aware - I've been told an internal incident report has been raised. Our instance also went down but it seems like its back now - so keep trying! Whilst it has not yet been updated, you can also check for issues via: https://status.atlassian.com/ Ste
  • Hi @Orit Gaon Atlassian is aware - I've been told an internal incident report has been raised. Our instance also went down but it seems like its back now - so keep trying! Whilst it has not yet been updated, you can also check for issues via: https://status.atlassian.com/ Ste
  • Hi @Gustav Rubiò Atlassian is aware - I've been told an internal incident report has been raised. Our instance also went down but it seems like its back now - so keep trying! Whilst it has not yet been updated, you can also check for issues via: https://status.atlassian.com/ Ste
  • Hi @Andreas Huber Atlassian is aware - I've been told an internal incident report has been raised. Our instance also went down but it seems like its back now - so keep trying! Whilst it has not yet been updated, you can also check for issues via: https://status.atlassian.com/ Ste
  • Hi @Jamie Warren Atlassian is aware - I've been told an internal incident report has been raised. Our instance also went down but it seems like its back now - so keep trying! Whilst it has not yet been updated, you can also check for issues via: https://status.atlassian.com/ Ste
  • Hi @khalid Not natively; a transition button changes one issue's status. I'd envisage this could be done via a script, an automation app - like Automation for Jira - or a workflow extension app like Jira Misc Workflow Extensions or JSU Automation Suite Using Automation as the example - this is how that would work: *…
  • Hi @Ashish.Singh No - that's the annual cost for the licences & maintenance (i.e upgrades, etc). Your own infrastructure to host Data Center would be a separate cost. This cost is difficult to estimate as even just at a simple-level, it could depend on number of users, number of products, number of apps, issue count, file…
  • Hi @Sean Wiese Can you provide the full rule? Mark's method of utilising the "Copy From..." function for setting field values is the ideal option for this issue - but if there is more to the rule it might benefit to see this :) Ste
  • Hi @starryeyes Native JQL does not allow for sub-queries within a main query. So you can refer to one single Epic Link - but you can't search for a set of Epics based on field values. As @Andrew Whitley mentions, you'll need an app for this with more advanced JQL functions - such as Scriptrunner This will allow for queries…
  • Hi Thomas, No worries - there's another app I found yesterday which might also interest you - see Optimizer for Jira Or if these apps aren't quite meeting your need, you can check out other options on the Marketplace! Ste
  • Hi @JasonB3 Making a minor modification in the JQL should make this work This is how I achieved this rule: * Trigger: Sprint Started in <<Board Here>> * Branch: JQL - JQL: sprint = {{sprint.id}} and status != Done * Condition: Issue Type (field) equals (condition) Subtask (Value) * Action: Assign Issue - specify user =…
  • Hi @Kmmaughs So this is how I built both rules (for reference). Rule 1: * Trigger: Issue Transitioned - FROM Status A TO Status B * Action: Create Issue - set Linked Issues: blocks Trigger Issue, set Labels: First_Task Rule 2: * Trigger: issue Transitioned - TO Done * Condition: Issue Fields Condition - Labels (Field)…