Comments
-
Hi Gisela, Try using just: issuetype != Epic it’s just JQL so you shouldn’t need the smart value there.
-
Great! Glad you got it sorted.
-
Hi Eszter, No, the basic Timeline is for a single project only. You can use Plans (formerly Advanced Roadmaps) to do what you want, but you will need a Premium Jira subscription.
-
Armenia! In honor of my friend Miro back in Dubai.
-
You are welcome.
-
You are very welcome.
-
Hi Elaine, Make sure that the Summary field is on the Edit screen for the project.
-
Already getting sad that this will end today. It's been great seeing everyone and meeting new friends!! For those watching virtually, make plans for Anaheim, CA next April!!
-
Okay, just a note, but this is a Business project not a Software project. And for these types of projects, the issues disappear from the board automatically after two weeks. I would suggest that you change the Status category for the List to Call status to be In Progress instead of Done type status. Then the cards will…
-
Ah, that's probably why then. Team-managed projects are very limited especially for user picker custom fields. I would suggest using a Company-managed project if you really need that functionality.
-
Hi Shivani, Not sure of the character limit - but you can probably count the characters in your image and determine that. However, it would be better if you created status names that were more succinct and not so long. Use acronyms or abbreviations if necessary. And, of course, the best thing is to reuse existing statuses…
-
Hi David, The Timeline is in the process of getting updated and should be rolling out this month so that you can see the proper nesting of Epics in the Timeline. You can vote for and follow along here for updates: https://jira.atlassian.com/browse/JWMCLOUD-111
-
Hi John, Just my opinion but I don't think this will happen anytime soon. And you should put in a Feature Request for it directly with Atlassian. This is just the user community - we won't be able to do anything about it here. But I am curious as to your use case for needing it.
-
Hi Casper - Welcome to the Atlassian Community! Try removing the Parent field off of the Edit screen. They won't be able to change the Parent at all if you do that - including just changing to another parent. But they would be able to clear it out either.
-
@Andy Price - Please reply inline to the thread so that readers can follow the conversation. And no, using Rebekka's query above takes care of that with the currentUser() notation.
-
Hi Andy, I would say most likely that it got deleted. There’s no real way to know that though. It could’ve been renamed. Regardless you’ll need to re-create it.
-
Hi Tyrone, Do you have a Default value of 0 for the custom field? Try adding that and see if it solves the problem for new issues.
-
Hi Hakim, I would first try by creating a new Kanban board for the project, and use it instead of the Scrum board. Go to Your Work in the top navigation bar, then select Boards and then View all boards. Next click on Create board and then choose Create a Kanban board. Use From Existing Project. Give the board a name, and…
-
Yeah, that’s the problem then. They have to be the exact same type with the exact same name. And if it’s a drop down, they have to have the exact same options.
-
Great! Glad that’s working for you now.
-
Yes, you should populate the cascading field with the values of the existing field. Then you can delete the old field.
-
Hi Philip, You CAN create multiple workflows for business projects (Jira Work Management projects). If your issue is that you can't see issues from multiple workflows on a Jira Work Management built-in board, then you can create a Jira Software board that shows the issues. You don't need to move the issues to a Jira…
-
Hi Albert, Check the Permission Scheme for the Project to make sure you have the Set Issue Security permission.
-
Hi @Jira Stuff There are a few ways to attack this. One is to use the Calendar gadget in a dashboard. Another option is to create a Calendar in Confluence and use filter from Jira issues to populate it. A third would be to get an add-on that would connect it to Microsoft Office - though this is limited functionality in how…
-
Maybe there was a problem at the time, but if you create the Custom fields in Settings > Issues > Custom fields with the EXACT same name as the one in the Team-managed Project, they should get copied over. You don't have more than one custom field with that same name in the shared custom fields above do you?
-
Hi Dima, If you are you wanting to see the group by for the Assignee, just create your Filter like it already sounds like you have done. Then create a Dashboard or edit an existing one and add a gadget for Issue Statistics. Connect it to your filter. Then use Assignee as the Issue Statistic. That should get you want you…
-
Great! Glad you found it.
-
You are welcome.
-
Answer is still the same - see above ☝️
-
Thanks, Bill! I was thinking of writing the same kind of article. I would also add To include screenshots whenever possible. And also to clearly state what type of project is - Jira software, Jira work management, Jira service management. And whether it is Company-managed or Team-managed.