Nic Brough -Adaptavist- Expert

Again, this has nothing to do with field type, I don't understand what you are trying to do here.

Could you explain what you have set up here? It makes no sense to have to "wait for attachments" - how are you attaching them? What are you doing that runs before the attachments are attached?

That's not the right way to get the classes you need. Have a look at https://library.adaptavist.com/entity/transition-original-issue-according-to-cloned-issue instead - it transitions another issue in a post-function, albeit with different criteria.

Welcome to the Atlassian Community! No, it's not saying it is taken, it is saying the name is invalid. You need to remove the periods in it. I suspect you really just want ioki as the name.

A delay is irrelevant here. You need to code for a validator to check attachments were added. You've got a problem with whatever you are doing to copy the attachments, not a delay.

These screenshots are simply of different screens (lists of fields), they're nothing to do with the field type. All I can say from these screenshots is that you need to add the fields you want to use to the screens.

You can't do validation on issue moves. You have a much bigger problem here - your process is broken. Moving an issue from one project to another is never part of a process, it breaks so many things. You need to revise your data structure - your projects sound like they are aligned to teams, which is not the right thing to…

That sounds like a botch to me. What post-functions do you have in the workflow?

Welcome to the Atlassian Community! What are their permissions? What are the symptoms of "can not create" (what's stopping them?)

How are you triggering the script? (Post-function? Listener? etc) Can you check the logs to see if it is throwing errors? Can you try the script in the SR console? You'll need to add a line to the top of it to point at a test issue to be cloned; def issue = issuemanager.getIssueByCurrentKey("ABC-123") 

TLDR: You are aiming to do Scrum, so I would create Scrum projects The project "type" in these cases is actually the type of the template, not the project. Confusingly, there's three ways people use the word "type" when talking about projects: * Whether it is team-managed or company-managed project * Whether it is a…

Ok, find an issue that has a SNOW number, go into the script editor for the field, and try putting the issue key into the test box. The tab beneath it will show you the execution log, including errors. I'd add a bit more logging in: if (!issue.subTask) { log.info "Not a sub-task" return } ... log.info customField return…

Welcome to the Atlassian Community! Jira has a linkedissue and linkedissues() function built in - see how to use them at https://support.atlassian.com/jira-service-management-cloud/docs/advanced-search-reference-jql-functions/

Yep, "include" is only going to work for guests if the included page or excerpt is in the same space as the page including them.

You've run into something that I think of as a design flaw in the original database. An issue object is a simple row in a table in the database, holding the current data for it. That's an intuitive and natural way to hold a representation of an object, the way most humans will think about it. But it's not the right way to…

This script should do it. Create a scripted field with a different name to "SNOW Number" ("All issues SNOW Number" for example) Make sure you set the "template" for the custom field to the same type of field that your SNOW Number is (number or text), otherwise you'll need a bit more code to convert the output to the…

The problem in your code is that you are getting the parent issue type, not the actual parent issue, but see my answer for a different way to do it.

You must be using one or more features that require a paid plan.

Welcome to the Atlassian Community! Yes, a viewer needs to be able to see the page that contains the content of an "include". The whole point of the permissions is to only allow authorised people to see content.

You can not create duplicate issue types. How would people know which one it is if you have two with the same name? Or Jira? The JQL "issuetype = Bug" could not work if you had duplicate names.

Welcome to the Atlassian Community! You can not add new categories. What do you think you want to add? How would it not duplicate one of the existing three categories? "Cancelled" is the same as "done" because "done" means "needs no further work needed". Your "cancelled" category is not a category, it's a status, one that…

No, that makes no sense, so you can't do it.

Is your AB-12345 an Epic in a team-managed project?

Welcome to the Atlassian Community! If you go to Premium, you get "Advanced Roadmaps", which lets you create issue types of many layers alongside and above epics, as well as renaming Epic and have it work the same.

Let's turn the question around - think of your users! Why do you want to stop them from using an issue link that could be useful to them?

@Nasreen Khan @zahar karet You need to do a lot of reading up on what AI, machine learning, and, expert systems are. If you get stuck, then the best place to ask is in fora dedicated to them; unrelated Communities (like the Atlassian one you have posted on here) probably won't have a lot to tell you. All I can do is…

Ok, that's really helpful. Thank you! I can now ignore "move" in Jira-speak. It means "update an issue" in this case. You are outside a Scrum/Kanban structure, so your story points will probably do what you need. I strongly recommend that you don't touch Scrum boards here, but project and Kanban boards could still be very…

It is now safe to rename Epics (I think all the apps that failed when you did it have been fixed, or dropped off the marketplace) Do not try to do it in the database. Use the UI. The best way to look at is in the Advanced Roadmaps hierarchy settings, where you can nominate other issue types to work at the Epic level, set…

You can do this, yes, because you've said you are on Jira Software premium. Jira is an issue tracker, so the most important object in it is simply "the issue". The core of Jira gives us base-level issues (which can have sub-tasks, as fragments of them. Sub-tasks are issue-like objects, but are always treated as a part of…

No, you won't lose anything if you do not become a paid user. What makes you think you've lost any of your work? Were you a premium user who downgraded?