Comments
-
Very good - if you have not created your free instance, you can do that here: https://www.atlassian.com/software/jira/work-management
-
Ah, so it sounds like there are multiple statuses mapped to the Backlog section of your board. I thought you were talking about an actual Backlog status. Team-managed projects are not very flexible. Can you share a screenshot of your board? I think that those projects may wrongly assume that if you want a Backlog then it…
-
Oh - there is nothing built into Jira that will show you that. You might be able to do something with the API, but I don't know.
-
Hey Alex, You are probably encountering this bug: https://jira.atlassian.com/browse/JRACLOUD-66006 You should vote for it and follow it.
-
Hi Edward - Welcome to the Atlassian Community! When tickets are created they go to the first status in your workflow. Typically, that will be the Backlog status. If you want them to go to a different status, you one a couple of options. 1. You can change your workflow so that the Create transition (the first line from the…
-
Hi Viktoras, You need to update the transitions to each of your Done category statues to have a Post Function that sets the Resolution field. That will cause the issue to get crossed out. For Sprints, only the issues in the very last (far right) column are considered completed. So you need to map all of those Done statuses…
-
Ah, so you are trying to use the new Chrome extension for creating issues for a JWM project. Have you indeed created a JWM project in your instance yet? You must have that first.
-
See the screenshot below. But you just add the gadget like I previously mentioned and then include the user's account id. This will show all of the user's activity across all projects.
-
They don't all have to use the same Issue Type Scheme (although they could) but each Issue Type Scheme will need to include the new Issue Type for it to be able to be used on the project.
-
Hi Emmanuel, Can you share the Conditions and Validators on that transition in the workflow? You probably need to add a Condition that allows the atlassian-addons-project-access project role to execute the transition.
-
Hi Berat - Welcome to the Atlassian Community! Workflows are associated with Issue Types. And both are associated with a a projects. So you can create an Issue Type Scheme and attach it to multiple Company-managed projects, which allows you to share the same issue type with multiple projects.
-
Hi @ULTRA Support Please see this article for further guidance. https://confluence.atlassian.com/servicedeskcloud/blog/2017/04/introducing-the-login-free-portal-for-jira-service-desk-cloud
-
Very good - thank you for the information Hrish!
-
Hi Sam - Welcome to the Atlassian Community! Are you linking the Proforma Forms field to a Jira custom field? If so, has that field had the Renderer changed in the Field Configuration to use Wiki style?
-
Hi Nate, Just curious why you need to keep adding groups? Do you have the organizations setup already? Are you using those?
-
Hi Ashley, Just curious why you would need to notify Opsgenie for the SLA breach and not just a regular Automation notification.
-
Hi @[deleted] - Did you ever get an answer for this?
-
It’s temporary as I just moved to Dubai, but here it is
-
Glad to hear you solved it.
-
Hi Atif - Welcome to the Atlassian Community! Try this for your query: duedate >= startOfDay(-1)
-
Hi Gabriel - Welcome to the Atlassian Community! You can use JWM projects for whatever kind of work you want to do. I actually use in a personal Jira instance to do DIY projects around the house, plan trips, etc. At work, it can be used with ANY business team - Legal, HR, Marketing, Finance, etc.
-
Thanks, @Jimmy Seddon - I am already hard at work. :-)
-
Hi Carmen, I guess the first question back to you is, why do you want to modify that field? What is it that you are trying to do?
-
@Martin Beke - Going to mark this one as accepted. You can request a feature change with Atlassian if you like.
-
You will need to set that third board up as a Kanban board if the Dev team is using Scrum. And in that case it should only be used for viewing and not bypass the built-in functionality of the Scrum board.
-
Hi Shaun - Welcome to the Atlassian Community! Sounds like that might be a bug. Are you doing a Create for the new issue or are you Cloning the first issue? The clone might help if you are not trying that.
-
Are you creating the task everyday no matter what happens to the task the day before? Or are you only creating the new task when the first task gets finished? If you are creating it no matter what, then create a rule with a Scheduled Trigger. It should be fairly easy to do.
-
Hi Lindsay, Yes, you can do that without it affect your colleague's access to other projects. However, it might not change the notifications - it just depends on how the notification scheme is setup for the project. But remove your colleague from the People section and see what happens for the notifications.
-
And now you have more than one reason to visit Dubai. HA!
-
Hi Wanda, Yes, you can do what you are suggesting. You can create two different projects using JSW for the Dev and JWM for the Hardware if you like. Then you can create a third board which would show a consolidation of both projects. Just be sure to create each project as a Company-managed project. Here's an article on how…