Mikael Sandberg Community Champion

The problem with using a JSW project as a IT support project is that the reporter has to have an account in Jira for it to work. You should consider JSM, since it allows unlicensed users to submit requests, and it has a separate customer notification scheme. And yes, you could use smart values to set the email domain and…

At my previous company I worked for we had a similar set up, but the driving factor was the workflow and it controlled when an issue moved from the Kanban board (used for research and review) to a Scrum board. By doing it this way only issues that were ready for development where added to to the backlog for the teams to do…

Yes, since boards are just showing what the associated filter is selecting you can use multiple boards to do this.

Yes, you can type in the email address manually in the to field, just hit enter after and it will add it. If you want to manually run the rule you would have to use the scheduled trigger, once you have configured it you should see a button that allows you to manually trigger it.

It depends on your project when you are using smart values (initiator and reporter are smart values). But the rule should have trigger when an issue is created. Here is what I would try, create a new rule that triggers on issue creation, and then add a comment to the issue and see if that works.

Instead of the initiator, try using reporter instead and see if that works.

Yes, if you have Jira Software Cloud you will also have access to Jira Work Management. You can easily check that by creating a new project, the first screen should show you a list of different project templates similar to this:

Did you start with one of the automations from the library? I just created this rule from scratch and it sent the email once the issue was create:

Is your initial status Open when a new issue is created? Normally when you create a rule when the issue is created you do not have to check the status as well.

Yes, Jira Work Management is the new name for Jira Core, you can check out this FAQ that Atlassian created when they announced the name change, https://community.atlassian.com/t5/Jira-Work-Management-Articles/Jira-Work-Management-FAQ/ba-p/1627315

I would use an automation to notify an external user instead of using a post function/notification scheme. The automation is not limited to only be able to send emails to internal users (access to Jira). Have a look at the automation library and the…

The hierarchy mentioned in the documentation is only available if you are on the Jira Cloud Premium plan, this is a feature that is part of Advanced roadmap. There are also apps on the Marketplace that would allow you to create a similar hierarchy.

@Melanie Beaudry Desjardins Correct, the hierarchy mentioned in the documentation can only be set if you are on the Premium plan. There are apps on the Marketplace that would allow you to create a similar hierarchy.

Note that you have to be on Jira Premium subscription in order to have access to Advanced Roadmap.

You may want to take a look at using a looped transition (allows you to perform an action without changing the current status), that way you can make the comment field required, and remove the Fix version field from the edit screen. 

I was looking for something the other day and found this t-shirt, still in the plastic bag. This was the second shirt I got, the original one is long gone...

Yeah, the commute is not something that I have missed at all. The commute anywhere around here is a mess...

My office is 36 miles away in downtown Seattle, which equals to about 90 minutes in traffic one way on a good day (40 minutes on weekends). But because of the lockdown and the growth we have had this past year, the office will be over capacity once we open it back up again so I will not going back to the office in the near…

Hi @Amir Hashemi, Welcome to Atlassian Community! It all depends on how your project is configured. A field can be set to required via the field configuration scheme or as part of your transition. If the field is only required when you move to specific status then you need to modify the workflow. If the field is always…

Hi @Mark McCubbin, Welcome to Atlassian Community! The Key cannot be set as the label, you can only assign the label to custom fields or the Name (which you can rename to something else as well). 

Hi @Bryn Wiragh, Welcome to Atlassian Community! The reason you the get notification that the created issue is hidden is because the filter on the board you are on may filter out the issue type you are using, or the initial status that the new issue is in has not been mapped to one of the columns on the board.

Currently that is not possible, but it is on the roadmap to be able to customize the portal view. If you look at the public roadmap this is planned to be released in Q3 2021.

One way you could do that and not give everyone site admin would be to extract the information via the REST API and present it somehow to the agents like importing it into Insight (if you are on the premium plan). There are a couple of customer apps in the marketplace, but I'm not sure if they can access the customer list…

Correct, the customer list is project specific, even if you have opened it up so anyone can register for an account. I have customers in one project that is no listed in the list. Also note that you control on the project level too if anyone can be added as a customer to the project or not. The global permission to allow…

Your agents should be able to see the customer list from within the project if you go to Customer & Channels: You should see these options if you click Back to Project, by default when an agent goes to the project they will be taken to the queue they last viewed.

No, moving the issue to a different project will not affect the Bitbucket integration. Jira keeps track of the old issue key when you move an issue to a new project. You could move the links, by renaming the branch, but for the commit you would have to rewrite the commit history because the integration is using the smart…

I'm in!

Perfect, thanks @Dirk Ronsmans , I must have missed that announcement. 

Thank you JSM team for doing this! To follow up on @LarryBrock question, when do you anticipate to release the REST API for the new Insight? And when do yo expect to have the migration path in place to get objects in the old Insight over to the new one?

This can be done either by using separate projects for each team and then use automation to create a ticket in each team's project, or manually move the request over, or as you mentioned have all the teams work out of the same project. It all depends how your teams work. I have a JSM project for HR, that is used for…