Mikael Sandberg Community Champion

Yes, you can have different workflows within the same project, as long as you are using a company-managed project. Team-managed projects currently do not allow you to do this. Note that an issue type within the project can only be assigned to one workflow, so you would have to have different issue types in order to do this.

Hi @Benjamin Marsh, Welcome to Atlassian Community! I have notified the Atlassian support team that is on here and should be able to help you remove that email from their do not send list.

Hi @Gabriel Palomarez, Welcome to Atlassian Community! Can you export the info in FB to either csv or json format? Those are the formats that the importer supports, besides Trello. Your other option would be to use the REST API to import your data. 

It is not possible to show Insight objects on a user's profile page. What you could do is store your users in Insight and set up associations there, you can then go to the user object and view the object graph. 

It is possible if you make your second rule to trigger on an incoming webhook, you can then trigger the second rule from the first one using a web request.

You can change the owner of a shared filter if you have admin access. Just go to Settings > System > Filter. Search for the filter and click the three-dot menu and select Change owner. Have a look at this KB for more details.

Short answer is no, you cannot see the status and assignee of the linked issue in the queue view.

Because you need to assign the request to your collaborators there is no way around it, you have to add them as agents which also means that they show up in the workload report. As @Joseph Chung Yin mentioned below, you could give them the role of Collaborators, but that limits what the user can do.

Hi @Fabricio Messia, Welcome to Atlassian Community! You can limit the access to a JSM project by only adding users/groups to the Service desk customer role that should be able to see it. If your external customer is only added to one project as customer, they will only see that project and nothing else. You can learn more…

No, in order to assign a request to a user that user has to be a JSM agent. You can allow Jira users to view requests and add internal comments when needed, but a JSM license is needed for any users that you want to assign to a request.

Hi @sashalivanov2007, Welcome to Atlassian Community! You should probably contact Solid Run Technical Support using this form, you ended up on this community because they are using one of Atlassian's products for their documentation. 

Yes, this can be done with automation. You would need to use smart value and the substringAfter separator to get the domain, something like this:

Go to admin.atlassian.com and select your organization. Then go to Settings > Administrators and from here you can add users as org admins.

Well, unfortunately the community does not have access to the customers instances, so we cannot do anything. Someone that is already an admin on your instance has to give you that access.

Hi @Kieran Watson, Welcome to Atlassian Community! You would have to contact your IT department to get help with this, we here at Atlassian Community do not have access to other customers instances. 

No, unfortunately an object can only occur once in an Insight field. There is a request to have that feature added, JSDCLOUD-10790, so I would recommend that you go and add your vote to it. 

Make sure that you save your changes to the hierarchy. If it is saved correctly the Parent link should work correctly.

What you see is correct, the way you have it set up in the picture means that Initiative is above Epic. Ignore the number, that is a bit misleading. You should read the list top to bottom, meaning that the level that is at the top is the top or the hierarchy.

Hi @Teja Vankayalapati, Welcome to Atlassian Community! When you configure the approval, on the second screen you should see this:

Okay, so that explains why the customer cannot access it. In order to access JSW issues you have to have a JSW license.

What type of project is the second project? A JSM project? And if so does the customer see that project if they go the to top level on the portal?

Hi @Nick, Welcome to Atlassian Community! Changes made via automations will always trigger notifications, the only way to not tigger them is to manually do a bulk edit.

Hi @Marc Smith, Welcome to Atlassian Community! There is currently and active incident with Trello, I would recommend that you go to https://trello.status.atlassian.com/ and sign up for updates to get notified when this one is solved and for any future issues. 

The short answer is no, you cannot change the position of that marker.

Attachments is coming, it is currently slated for Q3 2022 according the public roadmap. 

The issue will be linked to your repository if you are mentioning the issue key (JRA-123) as part of your commit, in the branch name or as part the description in a pull request. So you do not have to use a custom field to add a link to the repository in Bitbucket.

You can learn more about the integration here, but besides being able to see you Bitbucket repositories under Code, you can on each issue see branches, commits, and pull requests that mention that specific issue. You can transition issues in the workflow using smart commits or automation.

I would do it by using components, so every time your automation is doing the assignment, also add a component, like auto-assigned or something like that. You can then use that component to create a filter to show how many requests were auto-assigned.

Hi @Tony Parsons, Welcome to Atlassian Community! The error message is a bit misleading, what it means is that if you are trying to remove a status, or add an outgoing transition to a status that do not have one already you can only do that on an inactive workflow. So what you have to do is make a copy of your workflow,…

This is expected, and the announcement was made last month about this new feature, see Introducing Findable Drafts - a better way to start, pause, and resume your work for all the details.