John Funk Community Champion

Hi @seelye.naomi In your new instance, go to Settings > Issues > Sub-tasks. And make sure that Sub-tasks have been enabled and that you have at least one Sub-task type. If all of that is good, then make sure your Issue Type Scheme attached to the project has the Sub-task issue type included. 

Yes, you can add two statuses in that last column. See the example below. But just go to Project Settings > Board > Columns and Statuses. Then just drag the other status to the Done column. Then delete the column if it is still there but empty. All of the issues in the last column will be treated as Complete and will not…

Hi Christophe, I would create a rule using If/Then Conditions for each of the people. Then create the generic email and copy it into each of the sections. You will have to modify the same email multiple times if you change it, but it should work this way. Or you can create a separate rule for each user. Then if the email…

Hi Kenshi, What type of project are you using? Team-managed? Company-managed? Jira Work Management? 

Hi Sasidhar - Welcome to the Atlassian Community! What type of project are you using? Team-managed? Company-managed? Jira Work Management? 

Hi Screenadh, I would copy the workflow you are using now, then modify the new workflow to be what you want. Then add the new workflow to the Workflow Scheme used by the project. In the process of adding the workflow, you can choose which Issue Types it applies to. 

Hi @Prakriti Arora - Did you ever get this solved?

You are welcome. :-)

Within the ProForma Form in JSM, yes. You add the checkbox field, and then add a section for each value of the checkbox that then shows the cascading field in the that section. I believe you can then limit the options that are available in the cascading field at that point. But you would need to test that out with one. If…

Hi Neil, I would suggest that you add the Jira Service Management product to your instance. Then you can set up a portal with a form for the external users to fill out (which can guide them to give you all of the information you need up front), or you can have them send an email. Either way will create an issue in Jira.…

Hi Max, You can create an Automation Rule like below using the #lookupIssues functionality. 

Hi Screenadh, You might be able to accomplish with using different statuses, each with a different number of approvals. You can create an automation rule that fires when the Access field is changed (Field Value Changed trigger), that then transitions the issue to one of the two statuses based on the value of the Access…

Hi Conor - Welcome to the Atlassian Community! If you are using Company-managed projects, yes, you can easily do that. If you are using Team-managed projects, then no - because each project is independent of all other projects and nothing can be shared. 

Hi Julian - Welcome to the Atlassian Community! There's no built-in concept of "additional" assignees in Jira. An issue is assigned to one and only one person. You should need to an additional custom field to capture persons besides the Assignee. 

As Dave says, you can't go 3 deep like that with just the cascading field type. However, you can add a Form since it is Jira Service Management. In the Form you can do multiple levels deep using Sections in the form to do conditional options. 

Hi Matthew - Welcome to the Atlassian Community! You will need an add-on like ScriptRunner or Automation for Jira. Automation for Jira has a free Lite version and a paid Pro version. 

My understanding is that the list is people who are currently assigned an issue on the board. It would make no sense to show someone to filter by that doesn't have any issues on the board. 

Hi Christina - Welcome to the Atlassian Community! Can you explain a little more about what you have done so far, what you are trying to do, and what is not working for you? 

Hi @System support Yes, you can do that with a filter subscription or with an Automation for Jira rule using the #lookupIssues function. 

This sounds like it might be an issue with the time zone attached to your Jira instance. I recommend contacting Atlassian Support to see if they can pinpoint the problem. https://support.atlassian.com/contact/#/

@Jimmy Seddon - It was certainly warranted. Thanks for all you do for the Community!

Thanks, @Endre !

Hey Jack! No, I never did - in the short term at least. And then I quit using the app, so I don't know if it ever got fixed or not. Now I just use the built in calendar function in Jira Work Management. 

Hi Brad, No, you will not be able to get those in one column as the Epic Name only applies to Epics and not other issue types. And that field will be going away soon, so it will only be the Summary field anyway. So you will need Summary and Epic Link both. 

Hello and Welcome, Valerie!! We are glad you have joined us here. You have hit the nail on the head - JWM is aimed at Business team members who don't need (or want!) the complexity of Jira Software. And it's all integrated with Jira Software and Jira Service Manager as Dirk alludes. I will be speaking more about JWM at…

Hi Marius, You should be able to do that with the Automation For Jira app as well. There is a free Lite version and a paid Pro version. 

Have you removed all of the extensions? 

If it is the built-in board that comes with a Team-managed project, then the users you gave access to in the Project Access function should be able to see it. 

Thanks for sharing, Alex!

Hola Esade, ¿Alguna vez descubriste cómo hacer esto? Simplemente mantendría una de las solicitudes y cerraría la otra. ¿Qué información tendrían ambas solicitudes para que sepas que es la misma solicitud?