Can't the old threads closed automatically?

[Former Member]

Hi,

I am just thinking why can't the old threads closed automatically?

There are lot of old threads which might got resolved OR might not have proper responses, appearing in every forum.

If we have a functionality which close the thread with a tag "Expired" after 5 days (from the query raised date), that can help all of the volunteers.

I do not see any benefit in keeping those threads active!

Regards,

Nick Loy

[moazzam_ali · Accepted solution]

Hi

Sometimes I also think the same and it is possible easily to auto close or expire the thread but in that case it won't add any value to the threads. If it is done manually by OP or some moderator then it would be nice. I have seen a lot of threads where OP gets his answer and he posts Issue resolved and leave the thread open. I always try to advise them to close the thread.

If it is done automatically then answered, unanswered and open discussions all would be expired. Expired discussion means we won't be able to post in that thread. Right?? This is what I am assuming from expired thread definition

This will be workable if some human does that not the system. And I am in favor of putting some restriction to not to post in 3 months or more old threads. Sometimes it takes days or weeks and sometimes months to resolve some issue and I guess 3 months are fair enough. 5 days are not justifiable

Thank$

[Former Member · Accepted solution]

Sometimes it takes days or weeks and sometimes months to resolve some issue and I guess 3 months are fair enough. 5 days are not justifiable

Hi,

If it's just an information requirement - Normally threads get replies in days (Again not more than 5)

If it's related to normal issue - Threads get replies in days (Again not more than 5)

If it's VH issue related to production systems - This is not the right place to post, requestor should contact SAP using SMP.

I do not see such scenarios where requestor wait for months? May be I never faced such issue where I had to wait for months to resolve/get responses.

Months/Many days in getting responses is happening because of the junk/old data not because of other reasons I believe.

Regards,

Nick Loy

[JL23 · Accepted solution]

If you work in a bigger company, then 5 days are almost nothing.

SAP has such a nice CHarm process to make the environment secure, that means you cant even start developing something without having an approved change request. Not to talk about testing.

Of course there are discussions which can be be closed immediately, others need weeks, some months.  I still get some helpful and correct answer points from answers I had given years ago.

Without the "automatic" closure, you actually have evidence if the user takes care about his stuff or not, the auto closure makes this unresponsive user just look equal to someone who cares. Even more bad.  There is no real filter function in SCN to search only for answered questions, and you would miss a lot answered discussions which are not techncially marked answered.

I actually had some spare time last weekend, and I reviewed ANY discussions posted between May 15 and May 30 in the MM forum having an answer and have not been closed  . I wrote a single direct message and included all OPs into the distribution list:
You posted a question in SCN MM forum in last week of May. This question is still open despite of many answers. Is the issue really open and you don't follow up on it? If not open then please close your discussion. If you found the solution yourself, then share it. Check out the blog post 'How to close a discussion and why' in SCN.

Yes I had some good responses to the direct message. Yes some of them have closed their discussion from May, quite a few posted a solution. Some do not understand at all what "correct answer" actually means and marked their own "thank you" as correct answer. And some others which are already known as careless did neither respond nor close any of their discussions, they are just going on and posting the next question.

[moazzam_ali · Accepted solution]

Hi Nick

I have seen such threads many times. In fact if you go to my content you can see that I have asked such questions too couple of years back. This is when you get some issue where you are not getting some satisfactory answer and you have to do a lot of R&D for that. Sometimes with ABAPER and sometimes being functional only.

There are also some instances where we don't get some satisfactory answer from SCN and we have to raise OSS note to SAP and SAP gives some solution. In implementing/testing/UAT it could take days or weeks or months too. Though percentage of such issues would be very low may be in decimals but there are chances so we should have some space for such issues. I don't see any issue if we put some restriction in reposting in some more than 3 months thread.

What would you say about this?

Thank$

[Former Member · Accepted solution]

Hi Jurgen,

Issue can be asked/answered independently and I am sure that we are not helping the requestor throughout their change management process.

Issues are independent and almost all of the questions are related to particular system not for entire landscape. If it is for entire landscape then it falls under a solution where consulting comes into picture.

So these are just incidents which are system dependant and the restriction on number of days can help both (Requestor/Other contributors).

Any other thoughts?

Regards,

Nick Loy

[Former Member · Accepted solution]

Yes,

That is what my suggestion, better to have some restriction on number of days for each incident which can help both (Requestor and other contributors).

Restriction can be for 5days/3months whichever works!

Regards,

Nick Loy