John Funk Community Champion

For the next question, issues are stored in the database and connected to a project. Issues can be viewed and interacted with on a board or a list. But there is nothing magical about the board - it just helps you to see the issues. You can think of an Epic as more of a traditional project level grouping of issues. It's a…

Hi Tanya, You can do that with the Bulk change function. Click on the 3 dots menu in the upper right next to the Export button. Then choose Bulk change and follow the steps. 

@Jimmy Seddon - YUMM!!! I love General Tso's Chicken! I am having leftovers of spicy sausage and mac n' cheese :-)

Hello and Welcome @مرزوق مفتاح ! We are glad you are here!!

Hello and Welcome, Badr! We are glad you are here!!

Hi Aljoscha, Have you tried opening a support ticket here? https://support.atlassian.com/contact/#/

Hi Tanya, To change the Board name, click on the 3 dots menu in the upper right side and select Board settings. Then go to the General button on the left side. There you can change the board name. To change the project name, you must be a project administrator. If you are you will see the Project Settings link on the…

Ah, that's a great one!!

I don't believe you are going to be able to do project permissions through a plugin. You might be able to use the API to do a Project Role, but that is pretty doubtful as well. By native function, I mean just as how Jira already works in the application. 

Hi Katie - Welcome to the Atlassian Community! Can you share your workflow with us (screenshot)? You should be able to change the status back to To Do unless there is already another one in that workflow. 

Hello and Welcome, Şeyma! We are glad you are here!!

Ah, I actually missed the lookupIssues code in her example. Thanks for pointing that out! 

I am not aware of a plug in that does that. Why wouldn't you just use the native function in Jira?

Hi Todd, No, there's not way to get more visibility than it already having been assigned a ticket. You can vote on the issue there and following it, but that's about the extent that you can impact it being done any earlier than the thousands of other tickets that are already in there. 

According to that, then this one should work: {{issue.components.name}}

Hello and Welcome, Ryan! We are glad you are here!!

Hi Nicolas - can you share some screen shots of both? 

Hi Beatrice, Maybe try {{issue.components}}

Also, are you wanting to copy the Summary over from the initial ticket? If so, then it would look like: {{triggerissue.summary}} Access [Security KnowBe4+Git+AWS]

Hi Paula, Yes, you should be able to do that. What exactly are you trying to do? Or can you share the rule that you have so far? 

Hi Bayan - did this get sync'd up for you? It sounds like it might just take a long time depending on the number of repos you have. See this discussion from an earlier post. https://community.atlassian.com/t5/Marketplace-Apps-Integrations/Missing-Development-Panel-GitHub-Integration/qaq-p/937937 Also, make sure the…

Hi @Tomoyuki Sano , The quick answer is that Next-gen projects (now called Team-Based projects) are not very customizable right now, and certainly not shareable with other projects. So, no you can't use the same custom fields that have already been created. Nor can you use any of the shared schemes - workflows,…

Hi Kishor - I think you might can do this using the API. But the easiest way is probably to just download a CSV of your active users. This will include the date of their last login. Then you can sort it in Excel or Sheets by date. 

Oh - yeah, you can't link a board to a JSM project that way. Nor Next-gen projects for that matter. It won't keep the board from working (using whatever project you like in the filter). I usually create a generic Classic Software project called JSM Project. Then I use that one for the location. Or you can connect it to…

There is an Issue Auto Complete setting that you can turn off, but I am not sure if that affects the user picker related fields or not. You could try that. Got to Settings > System > General Configuration Click on the Edit Settings button on the top right Then change the value to No for the Issue Picker Auto-complete

No, you would need to move to Jira Software first. Then add the Jira Software Premium subscription. 

Go to Settings > Issues > Workflows Search for the workflow being used and click on Edit Then click on the line to the status - this is the Transition. When you do that, there will be a pop up that appears on the right side. There you can click on Post Functions. 

No, you are not going to be able to keep users from seeing any other users in user related fields - Owner, Assignee, Reporter, etc. 

Sure - Go to Settings > Issues > Workflows Search for the workflow that needs to be changed and select edit. Then change the view to the Diagram view. Click on the line (this is the transition) going to the Done status. This will pop up a box on the right side. There you can click on Validator. 

Sure - create your filter and share it. Then create a board based on an existing Filter and select the one you just created.