Comments
-
Hello, Unfortunately, JQL queries can only retrieve an issue type which is directly linked to an Epic. However, an efficient workaround would be to use a label or a component (that you name according to your Epic Name for instance) that you will be able to search easily using JQL. Let me know if it helped, Guilhem
-
Hello Jason, You field needs to belong to the Edit and potentially the View screen of the Screen Scheme used by your project. I would recommend to make sure that the field is in these screens that you can access from your Project Parameters => Screen scheme Let me know if it helped, Guilhem
-
Hello Dylan, I never tried this, but you can try using the following smart value : {{initiator}} However, this might not work for a JSM project as a client accessing the customer portal may not have a Jira account .. Let me know if it helped, Guilhem
-
Hello, I would suggest using a JQL condition in your automation rule of the following type : NameOfYourTextField ~ "Name of your component" (The text field of your issue contains your component) If the condition is validated, you can then set the component to the concerned issue. Let me know if it helped, Guilhem
-
Hello Matt, Have you tried having a look at the "Logs" of your automation rule ? It can help you understand where the problem is. Let me know if it helped, Guilhem
-
Hello Martin, If you only have a limited number of employees you can try using a "Created VS Resolved" gadget in a Jira dashboard that you can parameter to display the number of issues resolved by a specific user grouped by month.
-
Hello Dave, By admin created ticket, do you mean tickets created from the Agent view (using the blue "Create" button) ? If yes, your problem might be that you correctly configured you Customer Notifications (availble from your Project settings > Customer notifications) but not the Jira Permission Schemes (available from…
-
Hello Cyrus, Automation still works fine on my side, However is your rule a Global rule ? Because there exists a limitation in Jira in the number of Global rules you can execute each moth (1000 executions a month in the Standard plan if I'm remembering correctly). If yes, I would advise you to copy your rule in each…
-
Hello, Yes this is a normal message that you get when editing a workflow that is currently being used by at least 1 project. You have the choice to either keep a copy of the old workflow, or only keep the latest version. What I recommend is to only keep copies once in a while to be able to go back to a quite up to date…
-
Hello Serge, You c
-
Hallo Lukas, I'm not sure I fully understood your problem; should a screen pop up when you transition your issue ? If yes, you should check the Workflow to see if the correct Screen is displayed by the transition. Bitte sag mir, ob ich dir geholfen habe, Guilhem
-
Hello David, Have you checked the Validators and Conditions in the Workflow ? Maybe something was suppressed in the process.
-
Hello, Unfortunately, I don't know anyway to return the maximal value of a field. However, it is a bit longer but you can use an "If/Else" loop checking the different values of the B1 field (using a request of the type "If one of B1 field = XX") By stating with the highest values available for B1 and then going down in…
-
Hello, Indeed, you can use the following Smart Value : {{issue.reporter.emailAddress}} Let me know if it helped or not, Guilhem
-
Hello, You can indeed send an e-mail based on such criteria using an Automation rule that you will trigger daily using a JQL condition of the following type "Completion date" > startofDay(+3) You'll find information about Automation rules using the following link…
-
Hi Luis, Have you tried the Dynamic Forms option of the Extension for Jira Service Management Add-On ? I've implemented such a solution in an instance, it works perfectly and it's really easy to configure and maintain. You'll find it here . Let me know if it helped, Guilhem
-
Hello Serge, In my opinion, the best way to do it is your option 2 : it will create a major incident that will be seen from Opsgenie by other team, while keeping you original incident. You can then link the original incident to the major incident as you said. To me, changing an incident to a major incident is usefull if…
-
Hello, Indeed, this is weird because this should work (I does work in my instance). Are you sure that "Done" is the right status name ? Which statuses does Jira propose when you're building your search ? If it is the right status name, I suggest you to raise an issue from the Atlassian support portal (Suggestion and bug…
-
Hello Jayesh, Indeed, I confirm that this problem is probably due to the "Browse users and groups" permission that you don't seem to have access to. The only solution I see is asking a global admin for help, to grant you the "Browse users and groups" permission from the Settings => System => Global Settings menu. Let me…
-
Hello, When you close a Sprint in Jira Software, the stories you didn't finish are either marked as done in the closed Sprint, or moved to another Sprint. An issue can't be in 2 different sprints. As a result, your issues are either in a closed Sprint, or in a new one, which explains why your query doesn't return anything.…
-
Hello, Unfortunately, Jira Service Management is only compatible with versions 7.x or higher and hence not for Jira Software 6.3 😕 In case you plan to upgrade, you can find more information about compatible versions here. Let me know if it helped, Guilhem
-
Hello, Unfortunately, there exist no way to get around this issue at the moment. You can order the way transition buttons appear in the "View" screen using the "opsbar-sequence" property than you can add in you Wrokflow in the transitions (for more information about that you can go there), but not the Approvals buttons.…
-
Hello Mikhail, I think this is due to the fact that you are using a Free Atlassian licensing plan. The Standard licensing plan allows you to access this Mail -> Incoming mail menu and to configure the email issues creation. Let me know if it helped, Guilhem
-
Hello Adam, You can do that using an Automation rule : * Trigger your rule using the trigger "Field value changed", for the field assignee * Create a "New Action" of type "Edit issue" * Select your "Assigned Date" field, and assign it the current time using the Smart Value {{now}} Let me know if it helped, Guilhem
-
Hello, Yes, you can achieve that using an automation rule. You have to use an "issue field condition" filtering the values of your "Severity" field which should trigger an e-mail. You cant then customize your e-mail. Let me know if it helped or not, Guilhem
-
Hello Natalie, You can use what is called a Smart Value. The one you are looking for can be written the following way : {{Name Of Your CustomField}} Your field must be a number field if you want the comparison to work. Let me know if it helped or not, Guilhem
-
Hello Sai, Unfortunately no, as far as I know, there is no way to copy a custom field :/ I'm afraid you'll have to create a new one manually. However, if the 2 fields are the same and that you just want to add different values available for the field, you can simply add a new Context from within the field and specify new…
-
Hello Pavle, This configuration requires an Admin access to your Jira instance. In order to add your field to the desired issue type, you can : * Go to the Jira Administration menu using the cog in the top right part of your screen => issues * Go to the issue type screen schemes menu and click on configure on the one used…
-
Hello, Have you tried the advanced search ? You can use the following JQL to search more specifically on keywords : NameOfTheField ~ "keyword" Let me know if it helped or not, Guilhem
-
Hello, I'm not sure I fully understood your need but you can use the following process in order to change an epic status to "Done" if all of it's stories or tasks are "Done" too. This method can be adapted to complete a task when all of its subtasks are done too. * When : issue transitioned * If : issueType = Story * Rules…