Alex Koxaras -Relational- Community Champion

So @Michael Davison it's good to know that what I proposed back on September was the solution to your problem. How come you didn't try it back then?

Hi @Srinivas Jira doesn't provide this ability, to export one single project. Your solution would be to try an app from the marketplace, which will let you do this. However keep in mind that most of these apps (if not all) will export the whole instance first, and then separate configuration and issues of the specific…

But this is about jira server ;)

Sorry to hear that for you it's not the ideal way to see the description on the view screen. You may try the marketplace to see if there is an app for this kind of work you need to do.

Hi @Ouioui Zhou I don't think it's possible to do this. CMP and TMP have certain differences and this is one of them.

Hi @Travis Yes you can check if a value exist, like in the example below: First set the condition: "assignee != ". Do not enter a value on the value field Your condition should look like the following when you save it Now, if you try to move a ticket (i've place the condition on the transition from open to in progress),…

@Adam Stolt yes there is, and you can see it compacted under the (i) icon next to a field. If you hover on that field, the description will appear: There is no other way to show the description on the view issue screen.

Good to know!

@Mostafa Hegazy why didn't you say so? :) Then do this! I've tested it on my instance and only when all sub-tasks are done (not test-cases) then the parent is moved to done

@Mostafa Hegazy that's what I did in the scenario above. I have two different subtask issue types: Subtask and Test Case. They both work fine. * I would suggest that you share a screenshot of your rule's log * A screenshot of your issue type scheme * And the complete steps you are taking

Hi @Sandy and welcome to the community! You can use smart values to do that and especially the {{[date].plus[Unit]([number])}} which I've highlighted on my link. It's pretty easy to do so via Jira Automation. Or you can use and app to do that, like JSU, or scriptrunner which have calculated fields.

@Mostafa Hegazy hi, I've tried your rule and it works just fine: I've got 2 different subtask issue types. The first three are sub-tasks, whereas the fourth one is a "test case" subtask. The rule is triggered with every subtask move to done. And when I finally move the "test case" to done, it's also moves the parent.

Hi @jeroen_wilmes , * First of all you can generate issues by sending an email * You can generate issues by sending API request * You can generate issues by using the issue collector In addition to the first bullet, which uses jira standard mail handler, you can also use a JSM project and set it up in such way so as to…

Why don't you try the Atlassian University?

What @Édpo César said. The fact is that customers hold no license. Only agents do. 

Anyone who will talk/chat/reply to your customers is considered to be an agent.

Hi @Admin ProjectDome and welcome! You don't need license for your customers. You can have as many as you want. Only agents require license.

Hi @Kevin H. , If I understood correctly, you want to either insert a condition or a validator within a workflow. From what I know, out of the box you can use both, and due date is available as a field: Validator: Condition: Condition will check for the due date BEFORE transitioning the issue, whereas validator will check…

There is no edit screen on cloud @Adam Stolt. Besides this take a look at my transition screen:

Strange..

Hi @Adam Stolt and welcome to the community! Well, when you create these custom fields you can add a description. This description will be visible on these fields. Now, if you want a more "custom" approach, you can create a new field configuration, associate it with the specific issue type you are interested in, and then…

Hi @Katrina Thacker and welcome to the community! Try using the advance editing like in my example below. I've tested it and works fine. "checkboxes" is the name of my custom field of type checkboxes:

You've placed the refetch after the issue created and before the IF statement, right? Do you have an app like JMWE, JSU, scriptrunner etc which let you run scripts on the workflow? In addition, I would raise a support request to Atlassian to let you have the integrated proforma, instead of the app.

This is a component. Not a rule. Just search for re-fetch data. However there is no guarantee that it will solve your problem. Try it and kindly report back!

@Aron Gombas _Midori_ yes, it will do the trick as I mentioned here: You can't have this exact representation of your issues. You could use the "recently created" diagram, which will distinguish the resolved/unresolved, but its representation will be very close (created vs resolved will do the trick as well). @Thomas M I…

@[deleted] What you are looking is an Epic issue type. The "Project type" you are referring to is a custom field, with custom values. Now, this list you are showing me on the 2nd screen could be the result of automation done either within its workflow of via Jira Automation. As it seems, this automation is triggered on the…

So many great choices from all of you people! My cup of tea would be either somewhere in the Middle earth and close to the Shire, or traveling with Telemachus and Yumi, as Ulysses in the deep space, trying to find my way home!

Before doing anything, you have to make sure that the screens are not sharable with any other issue type. * Project settings * Issues * Screens * Click on the create screen of your issue type On the screen you will see, search for resolution field and remove it. Now, if there is NO resolution field there then two things…

@Manoj Pawar you are trying to add a status (with the same name), rather than inserting the existing status. When you type the name of the status, try selecting the result, instead of click add new status.

Hi @Thomas M and welcome to the community, Although I saw that this ticket refers to the server version of Jira, I would assume that it will be the same as Jira Cloud. Short answer to your question, as you put it, is "no". You can't have this exact representation of your issues. You could use the "recently created"…