How to mark issue in Jira as resolved when marked as done in app?

[stoltm]

Hi there,
would it be possible to enable the app to mark an issue as done/resolved in Jira, when marking the issue as done in the app?
Maybe I am not doing that one correctly, but I always have to go to Jira to resolve it there as well.
I think it should be possible, right?

Thanks,
T.

[johannesjo]

Hi there! This is already kind of possible with Transition handling:

[johannesjo]

Would it be possible to provide an option that let's the user chose wether it constantly updates itself and would not create "duplicates" in the app?

Not sure if I understand the last part. What do you mean by creating "duplicates" in the app?

[stoltm]

@johannesjo sorry for being so unprecise.
What I meant is that the way the app works now you'd basically create duplicates (as you mentioned earlier). If there is an issue in Jira it would be "alive" there and there would be a task in the app. That's what I mean by duplicate.
Let's say the issue would get rejected or changed or re-assigned to someone else, the task in the app would not be adapted, deleted (means not be synchronized in the app).
I would not like to have to update the tasks manually and usually I would not add to much information myself in the app. But I would like the app to read and update what's happening in jira. (And for instance the actual reason why I wrote this issue to be able to make an issue as done from the app.

[johannesjo]

I understand. Currently you get a warning when try to work on a task that is assigned to someone else (if you configure it), but I agree that it might be nice to have some way to handle the case you described. I just don't think that the task should be deleted (there might me time tracked on it or some important information, etc.) but maybe we can open up a dialog or different dialogs for when:

1. A jira issue task is assigned to another user
2. A task changed it's status on the server to done
3. ...?

And then allow a couple of options:

1. Mark the task as done (or maybe remove if no local changes have been made to the task)
2. Open the issue in the browser
3. Ignore
4. ... ?

What do you think?

[stoltm]

Precisely. That would be rad!

I myself would be happy if one of the options was to delete the task.

[johannesjo]

I am open for adding this feature, though I probably won't work be able to work on it myself anytime soon.

Best way to move forward would be to open up an issue with a short description what we want to implement and referencing what we discussed here.