Jack Brickey Expert

Is the JQL an actual cut and paste? I see an error - missing “QC”. You also have an unnecessary “ preceding resolution. now I’m not sure that is really your issue but something I noted. here is what I think your JQL should be… resolution = Unresolved AND status = "Work in progress" AND "Ticket type" != “QC" this should…

In fact Automation is precisely what makes this work in JSM. Please inspect your current rules especially under Legacy Automation for an existing rule. Given your point about previously working I suspect the workflow changes may have broken the rule.

@Jango Hemmes , I wonder if you need to post a new question if you are seeking assistance?

You don’t “login” as an administrator. Rather you are designated as an administrator. If you are not currently an administrator you would need to discuss with the current admin and see if they are open to give you these permissions. Generally speaking these permissions are not given to many users given the opportunity to…

Yes it changed in the not too distant past. It is a bit frustrating when there is inconsistencies in UX implementation within a single product.

edited/corrected… Click on any of the request types and it should take you to the desired configuration screen.

In top right corner next to your avatar you should see a cog icon. Click that and see if you have user management.

If you don’t see user management at admin.atlassian.com then you are not a full Jira admin. If you believe you are please share image of what you do see.

Go to administration (cog icon)> user management find user and revoke access

Your #3 should do the trick. You should see your values there under Options and you click edit options.

Thanks for the update @Monique vdB . Do you think we would benefit from using an issue tracker rather than current various means? I’m not sure where we could find such an application though? 🤣🤣🤣

To share a board the individual specified by the email address would have to be a licensed user in your jira instance.

I suspect this is because your issues are non-edible once they are in the resolved status. If you have just a couple of these just re-open them add your attachment and close them again

yep...

Sorry for the jumbled post it was resulting from dictation. I have corrected in the point is do you want all JSM issues from the project to appear or just certain ones? If certain ones how are they identified? You don't need to necessarily change your JSM workflow. However, mixing two completely different workflows on a…

well that is a different question. I see that you were on free so you're roadmap options are pretty limited. Are you using CMP or TMP projects. If CMP you need to go into Board settings and enable the beta feature. If TMP then you need to go under project settings and enable the feature. Romaps work under the epic…

@Corinne Dent , great presentation and explanation. Definitely a useful article that I can refer other community members to in the future. Thanks for sharing!

geez... missed it in title! DOH! Much of what's presented here applies to CMP as well it's just appears a little bit different.

i assume you have other fields you are mapping since you cannot create an issue without, at a minimum, Summary. to determine what fields are required for your specific case try creating an issue manually and assess required fields.

Thanks for sharing @Corinne Dent . For the benefit of the reader, it is worth mentioning that the video is illustrating TMP project. If using CMP things will appear different.

are you the jira admin? can you share a screenshot of what you're saying when you hit the wall?

Hi Daniel, See if this article help you out - create-issues-using-the-csv-importer 

You can certainly include JSM issues on your JSW project board if that is your goal. You simply need to edit the underlying board filter to include the desired issues. The question I would have to be able to comment further is how would you identify the specific JSM issues to include on the board such as label status etc.

I have never personally heard of elastic until now. As I was curious I did a bit of googling and found this FWIW - Elastic-actions-jira 

If these other users have JSW or JWM licenses and you want them to be able to browse and comment on JSM tickets then simply ensure that they have browse and comment permissions for the specific project in question. this will not require them to have a JSM license.

Ultimately what we’re looking for here is a discrepancy between queries. Fundamentally there can be no other real answer. My point is that whenever you’re looking for an answer to why the numbers don’t add up it’s because of A difference in the queries. Understanding that can help track down why there is a difference and…

You might find this article helpful - migrate-between-team-managed-and-company-managed-projects it is certainly a manual process and not perfect as some things can’t be easily transferred in the”move” process like custom fields.

To be clear issue layout does not apply to boards. They apply to issues in a project. for reference - configure-field-layout-in-the-issue-view 

Note that the import use Simple Date Format here is one reference - SimpleDateFormat 

You can use the raise a request on behalf of feature to open an issue on behalf of your customer. When you do that you basically are creating the issue via the portal setting the reporter to be your customer and choosing the correct request type. Once you do that JSM will send a notification to the customer that the issue…