Ste Wright Community Champion

Hi @[deleted] This will depend what Board features you have turned on. You can manage these features: * Go to Project Settings > Features* Backlog - if this is active (without Sprints) - your Board will have a Backlog where issues go when created. You need to "drag" them from the Backlog to the Board. The Backlog is on the…

Hi @kalaimani Great! In your case, you can actually manage both rules (set initial due date and set status-based due dates) in the one rule - it will look like this: * Trigger: Multiple Issue Events* Events = Issue Transitioned, Issue Created * Condition: IF Block...* IF... * Sub-Condition: Issue Fields Condition* Field =…

Hi @Bill Sheboy It's probably not needed - it was a "just in case" re-fetch to ensure the rule stayed in order :) Ste

Hi @Leonardo Zevallos Guzman There's 3 default roles you can assign to users - Administrator, Member, and Viewer. See this help page for a full comparison of the 3 roles, but Members and Viewers do not have the permissions... * Administer this project - i.e Project Settings access * Delete any issue So it might be possible…

Hi @kalaimani No need to accept the answer until you have the response you need :) You've not directly answered my questions - it'd be good to get these responses. Otherwise the rule will be possible to build, but I anticipate it'll have flaws in its logic. Another question is: * Can a user move back a status? If yes, what…

Hi @Kerry Hope There should be no need to duplicate the Actions - you can bring them all into one place using an additional Board, assuming these are all Company-managed Software Projects If Team-managed and/or Work Management, the below might still work with some caveats (eg. Location Project must still be a CMP Software…

Hi @kalaimani This will be possible, but can I confirm some queries about the logic? * I assume there's an Automation Rule or Post Function that sets the initial due date when the issue is created - is this always the case? * What is a due date has been removed - how should the rule handle this? * Can a user skip a status…

Hi @Marcus_palm This should work: project = APPEN AND issuetype = Bug AND status changed TO Done DURING (2023-11-10, 2023-11-22) This does assume you want all issues (whether still in Done or not) - or if you only want issues still in Done, you could add that in after Bug: project = APPEN AND issuetype = Bug AND status =…

Hi @Nhung You need to create the Custom Fields on the Company-managed side first, see how to do that on this help page Once created, you need to move data from your existing fields into the new ones. In my opinion, it's easiest to do this prior to moving as global custom fields can be added to Team-managed screens - so you…

Hi @Talles Silva I'd recommend using variables for this - and then IF/ELSE conditions to set the date. The rule might look like this... * Trigger: Field Value Changed* Fields to Monitor = Priority * (1) Action: Create Variable* Name = PreviousPriority * Smart Value = {{changelog.priority.fromstring}} * (2) Action: Create…

Hi @MahanthPrudhvi You can have a different View Screen to Create/Edit using Screen Schemes - this works in Cloud. This doesn't stop a user editing the field, but it makes it much more difficult, as the user would need to workaround the field being uneditable on the Screen. --- Alongside this, you could use Automation to…

Hi @Talles Silva This should be possible, but can I confirm the logic for this rule: * How does the Priority check relate to the date? * What logic defines the date set? An example (and/or the current rule you've built) would be beneficial here :) Ste

Hi @Michael Kazuto Hardenson Medina Lagos Is it possible this is linked to this suggestion - https://jira.atlassian.com/browse/JSDCLOUD-6369? Ste --- And in Spanish (according to Google Translate)... ¿Es posible que esto esté vinculado a esta sugerencia: https://jira.atlassian.com/browse/JSDCLOUD-6369?

Hi @James Holding This isn't a feature available at the moment - there's also not milestone lines at present, but it is suggested, check-out JSWCLOUD-17652 Although not in a timeline view, an alternative is to use Automation to ensure dates aren't pushed past a certain point - for example, a rule could check all Issues…

Hi @virginiepitters When you say manage your computer equipment, can you confirm what you mean? Do you mean track them as assets? If yes, I'd check out Asset Management, which is included with Jira Service Management Premium/Enterprise. Ste

Hi @Richard Branch This is possible! This should work (I've not included the Trigger/Conditions as I assume you have those from the other rule): * Action: Create Variable* Name = dateDiff * Smart Value = {{issue.customfield_123.diff(issue.customfield_10456).minutes}} * Action: Log Work* Time Spent = dateDiff * Date Started…

Hi @Evan Turner This should work... * Trigger: Field Value Changed* Field to Monitor = Story Points * Condition: Issue Fields Condition* Field = Issue Type * Condition = equals * Value = Task * Condition: Related Issues Condition* Related Issues = Linked Issues * Link Types = split from * Condition = Are present *…

Hi @Christian Fischer Apologies, I wasn't sure which option was required above. Rule would look something like this: * Trigger: Issue Assigned * Condition: Issue Fields Condition* Field = Issue Type * Condition = equals * Value = Sub-task * Condition: Issue Fields Condition* Field = Assignee * Condition = is not empty *…

Hi @Christian Fischer This rule works in Cloud; I can't be sure it works in Server but give it a go and let us know if there's anything which isn't available: * Trigger: Sprint Started * Branch: Related Issues * Type = Issues in the sprint* Branch-Condition: Issue Fields Condition* Field = Issue Type * Condition = equals *…

Hi @Christian Fischer This should work: * Trigger: Issue Assigned * Condition: Issue Fields Condition* Field = Issue Type * Condition = equals * Value = Sub-task * Condition: Issue Fields Condition* Field = Status * Condition = does not equal * Value = In Progress * Action: Transition Issue* Destination Status = In…

Hi @Anton Efimov With a little more testing (assuming this is Company-managed), it seems a user needs these 2 permissions: * Browse Projects * Administer Projects So whatever Project Role a user has within your Project, that role must have access to the 2 permissions above - often Developers/Members don't have "Administer…

Hi @Hizkeel Khan This should work: * Trigger: Scheduled* Run rule every = 1 Hours * Run a JQL search... = TRUE (checkbox)* JQL - status = "Code Review" and status changed BEFORE -4h * Only include issues that have changed... = FALSE (checkbox) * Action: Send Email or Comment on Issue* Populate details as needed --- A few…

Hi @Anton Efimov The field is a searchable drop-down - so it'll show a range of users, but you can search via a user's name and it should also show up as it searches. The Driver also has to be a Project Administrator. See more information on this help…

Hi @David Vermeir At present, the Epic Link is only used by the official Epic issue type (even if a custom one included the word "Epic") Atlassian are deprecating the Epic Link field though, replacing it with a generic Parent field in the near future - check out more details on this help page Ste

Hi @MARCOS CUEVAS VEGHEIM I believe it responds based on your language settings. To check these: * Go to your profile icon > Manage account * Select Account Preferences from the top navigation bar * Check your language setting - and change it if it's not in your preferred language Otherwise, according to this answer, you…

Hi @David Vermeir I tried this; in relation to creating Child Issues, this worked for me - I could... * Create child issues (based on the hierarchy) using the Add a child issue button on the main issue view (just under the Summary) * Add the parent issue to an existing issue using the "Parent Link" field --- In relation to…

Hi @Arne Theisen That's the issue - the Epic level cannot have sub-tasks below it - there are feature requests for this: * JRACLOUD-72060 - Creating Sub-tasks on Epics ^ This also includes Issue Types set at that level also. To remedy this, move Task to a different level, or remove it entirely so it defaults to Level 0. Ste

Hi @Yingyi You should be able to do this. But is it... * A single linked relationship - i.e one dependent issue, one issue depending on it, or... * A multi-linked relationship - eg. one dependent issue, with one issue depending on it, and another depending on that, etc. Ste

No worries :) If this did help, could you accept the answer - so others know this can help them too? Ste

Hi @Roqya Mokhtar I'd check out the following options... * Virtual Agent (on Slack) * Automation (eg. this could send an out of business hours response) Let us know some specifics about what the rule should do, and we can provide an example of how Automation can help? :) Ste