John Funk Community Champion

Yes, I have done that several times. Just create a board (or copy an existing board) and then create a new filter for that board that references the JSD project. The only drawback is that you cannot link the board to a Location for a JSD project. It has to be linked to a classic project. So I have a generic classic project…

Glad I could help!

Sure you can do that. 

Work never moves backwards in Kanban. If it fails you create a Defect (sub-task type) or a Bug. A Defect means that something is broken and the parent story cannot move through the process until all Defects associated with it are fixed. Defects run through the same process as the story. Bugs are noted as something not…

Yes, our last column is Done. But we also do not do Sprints - we just use Kanban. We can report on where (meaning what status) the cards are in and how long they are in each status and our lead time - how long to complete each card from start to finish. 

Hi Dharmesh, We have actually done something similar using a single workflow. We have all of the statuses in the workflow. We then have a custom field called Dev Needs. That fields is a checkboxes type field where you could put in the values of Integration, Beta, and Pre-Prod. So a user could check one or none of those…

This image is not an actual screenshot of the Workflow in Jira is it? Can you include that? Also, what statuses are mapped to the Backlog column on your board and what statuses are mapped to the first column on the board? 

Hey Harrison, Take a look at the Context for each of the custom fields. Sometimes they are based on Issue Type, too, and not just Project. 

Hi Livia - Welcome to the Atlassian Community! If you are doing a bulk move, at some point in the process it shows a mapping between statuses that are different in the two workflows. It usually defaults to the first status alphabetically. In this case, that's Blocked. Can you describe the exact steps you are doing? 

Hey Samuel, Can you share what you have so far? And what's not working as you would hope?

Hi Boris, Yes, there is definitely an issue with Automation For Jira not currently being able to handle Epics right now. You would need to find another way to make that link. All of your conditions apply to the issue being created. So there's no real check to see of the issue has an epic or not. Try using a Condition with…

Sounds good - happy to help!

Hi Weeda - Welcome to the Atlassian Community! You can do it but it is a little convoluted. You would setup Issue Level Security for the project with the Epic. Then apply the Security Level to the Epic itself. In the security level you would grant access to the all users basically so more than just the external user can…

Sure - what I do in cases like that is populate a hidden field. I have created a custom field with a checkboxes type (or you could use a Select list (single choice) field type). I make that field hidden in the Request Form and prepopulate it with a value of Yes. I have ingeniously named the field Generic Yes field. :-) So…

Hi Giorgia, Is there something that is different about that the issues created under each portal group that could be used in JQL? For example Issue Type or another field? 

Ah! I missed the Map field values box. Thanks for the correction!

Hi @Shankar Subramaniam - Make sure the values for the Asana status in your CSV match the statuses that you have in Jira. You might need to do a mass update in Excel to change the values, but you can't map In Progress to In Process for example. In other words you can't make the individual values just the fields themselves.…

Hi Mark - Welcome to the Atlassian Community! One way is to create a custom data field for Original Due Date and the populate it when you create the ticket. You can actually automate that using Automation For Jira - that way the field can be hidden and still get populated. 

Great - thanks, Julia!!

Hey @J_Nova - Welcome to the Atlassian Community! Where a card can go when you drag it (or change the status) depends on the underlying workflow for that issue type on that project. Make sure there is only a transition from the Backlog status to the Status of the first column to prevent it from going to other columns. 

Check the Field Configuration for those Issue Types on the project. See what it says about the Reporter field. 

Hi @hellok , When I logged in Friday I was able to see the score and the breakdown. Today, I can't either. Let me see if I can get more information. 

Hi Heather, Out of the box Jira will not provide that functionality when you clone a ticket. You will need an add-on such as Deep Clone. 

You can remove the field from the Edit screen if you like. But you have to have a value for the field to create it. 

I don't know why it allows that, but it doesn't change the fact that the Reporter must be entered to create the issue. It has to be on the Create Screen. 

Check the Permission Scheme for that project to make sure you have the Modify Reporter permission. 

Hi @System Admin - Welcome to the Atlassian Community! Why not just create a filter to show those issues? Then you can use the filter in a Filter Results gadget on a Dashboard. 

Hi Seema - Welcome to the Atlassian Community! You can create a filter like: Project in (ABC, DEF, 123) and issuetype = Epic

Hi Charlie, Have you tried a filter like: (Project = PROJECT1 and Problems = abc) and (Project = PROJECT2 and Problems abc)

Hi Pawhan - Welcome to the Atlassian Community! You should also be able to use Jira Miscellaneous Workflow Extensions (JMWE) add-on to create a custom validator. @David Fischer