Comments
-
@Leonid Danilenko This is an Atlassian Global community page, used to connect multiple users of their tools. If you want to speak with Atlassian support directly, open a support ticket via the link: https://support.atlassian.com/ I believe that there, Atlassian support will be able to provide other information.
-
@Margarita Ochigava , welcome to the Atlassian Community! There are some open incidents for the Atlassian Cloud environment. You can consult the product and cause here: https://status.atlassian.com/ Atlassian will keep us updated through the page for each product and its incident.
-
@JayJuan Jones , Here is the REGEX function that will make the email work in the following format: test@myco.state.us REGEX: [az]*[@][az]*[.][az][.][az]* Description: [az]* = test [@] = @ [az]* = myco [.] = . [az]* = state [.] = . [az]* = us As I told you, REGEX is something that will only accept something within that very…
-
That´s a great news!
-
@Charles Cain Just in the ACTION of editing the custom field of Start Date and End Date include the smartvalue: {{now}} Then Jira will populate the field with exactly the date and time the transition was performed. Hope this helps. Let me know if you have any question. Regards, Fernando
-
@Nicolle Diniz Go to project settings; Screens; View and Edit screens of the issuetype that will have the issue created; Add the "Epic link" field. Test again. The error occurs because the "Epic link" field is not available on the issue screen that will be created
-
The idea is not to copy the value of the "Epic link" field from Epic itself. Edit the "Epic link" field of the created task, making it assign the Epico that was carried over. It's a functional rule, if you do as I showed in the print you'll see that the result is safe.
-
@Nicolle Diniz Here's a very simple way for you to do this. TRIGGER: ISSUE TRANSITIONED: CONDITION: issuetype = EPIC ACTION: create issue. The detail you should note is that you should use the "Epic link" field and not the "Epic name" field; Also, you can directly put this EPIC LINK value when defining fields for the new…
-
@Ben Weisman , Go to the project settings; Click on "Details" The last option on the screen will be "Default Assignee"; Set the value "Project lead". Click on "SAVE CHANGES". After that, all issues created in the project will come with the assignee (project lead)
-
@Ehsaan Gaffar , welcome to the Atlassian Community! Yes, once added to the ticket, the participant is notified of each new comment added to the ticket, just like the reporter.
-
@Seth Clayton Does this research project fit the context you set up for the field? Particularly I don't think it's a good idea to apply context to "user picker" type fields. But if this project already fits the context you have set up for the field. I would recommend you to contact Atlassian support:…
-
@Seth Clayton Please check this: Access the custom field and click on "Details"; Make sure "Search Template" is checked as "User Picker & Group Searcher". This in Jira makes the field's options searchable. See an example: If that doesn't work, let me know.
-
@Christian Delgado Because it contains special character '#', the field in your search will not exclusively show it. Jira will list all fields and you will need to manually search for the field by mouse: If that doesn't work, let us know what the custom field type is so we can continue to analyze. Fernando
-
@Jimmy Seddon , thank you
-
@ext_mazanini Si su idea es configurar SLA's para comenzar a medir el tiempo que cada problema pasa en cada estado, debe seguir esta documentación aquí: https://confluence.atlassian.com/servicemanagementserver/setting-up-slas-939926373.html Si necesitas ayuda aparte de eso, házmelo saber.
-
@Seth Clayton I understand that you stated that you have already reviewed the permissions and etc, but some things that if you haven't seen it and you can check it out are something like: Check the "browse users and groups" global permission if the groups you and the rest of the team participate in are within that…
-
@Christoph Kleinschmidt There's a way you can do this, but you'll need to do something about this idea: First of all, the content you write in red that should be taken to a custom field, you have to make this content a unique comment. No other information that doesn't need to be copied, for example. This is because I will…
-
@maria.quintana , Just update: First value: {{issue.customfield_10155.child.value}} Condition: Contains regular Expression Regular expression: (Broken light switch|Emergency lights not working) I think that´s right now :)
-
@Rich Evers Glad to hear it worked! Please click "Accepted Answer" to help others in the community find this solution faster. Have a great weekend :D
-
@maria.quintana , Hey, try this: First value: {{issue.customfield_10155.child.value}} Condition: Contains Regular Expression Regular Expression: (Broken light switch || Emergency lights not working) I believe this works to you. If you have problems, let me know. Regards, Fernando
-
I think I understood and it became clearer. Just to ensure: If a subtask is created even after the Story has been completed, then the subtask should automatically move to TO DO while the Story should automatically move from DONE to IN PROGRESS. Here's a tweaked version of automation of how it might work for you. Details: -…
-
@Vitoria Treib , Clique em "Workspaces" no Trello e você verá a seleção de WorkSpaces onde você pode atuar ou foi convidada. O da empresa deverá estar lá. Assim que você clicar no Workspace para acesso, a página irá carregar e te mostrar os boards daquele espaço junto com todo o conteúdo daquele workspace. Segue print: Se…
-
@Rich Evers , As I understand it, you want the following: If a new sub-task is added even after Story has been completed, and that same sub-task is transitioned to "IN PROGRESS" your Story must also go from DONE to IN PROGRESS. Following this idea, the simple thing you should configure is like this: I did the automation…
-
@JayJuan Jones Just complementing with information, you can use a REGEX validator, but this can restrict the way this is done a little bit. See how: - In the transition of the flow where you want to include this validation, click on "Validator"; - Add the "Regular Expression Check" validator; - Define the field that should…
-
@SAVANNAH HUGHES , welcome! You can do this by configuring the flow, here's what to do: Create a canvas in Jira Here's how to create: https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-screens/ After creating the screen, follow this step by step: Access the project settings; Access Worfklows…
-
In that case, I believe you should set the behavior of the CategoryRF field, using the Sub-Category field Like: IF ELSE { ("subCategory !="Conversion costs (cups)") subCategory.setRequired(false) subCategory.setHidden(false) subCategory.setReadOnly(false) categoryRF.setRequired(false) categoryRF.setHidden(false)…
-
@Michael Wolfe Try changing "none" to "null". This is because interpretations can change. "null" = EMPTY "none" = no value If that doesn't work then you can go on trying some combinations in this ELSE. Something like RF != Plastics categoryRF.setRequired(false) categoryRF.setHidden(false) categoryRF.setReadOnly(false) I…
-
@Michael Wolfe I don't know exactly why this happens. Something like what you describe has never occurred to me. It could be something with the order they are arranged, try changing the order and see if the behavior is still the same.
-
@Michael Wolfe If you don't want to assign behavior to each field option, you don't need to include such a large load. I believe that following the example I gave you will get a good result because the second IF or ELSE will make the field behavior in Jira be the default with all other options in the other fields. But I…
-
@Peter Strömberg For Jira Software-only users to see this internal link, you would need to release the Jira Service Management license for them as well and add them to the project. If that doesn't happen, the only way these users can make comments on this type of ticket is if it is the "Reporter" or a user with whom the…